Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6e89b08b16d332175485b3904d7512ebc25a70e763718320aaf4ca4186e15ad2

Tx prefix hash: 731539a34e2c8d5198fbd7c4e7ff1a9705bcf083dea0dad640a3e402badd5127
Tx public key: d5bbcc4451ed30f236f63f06c5293979b2c3e16325e9e60f453cd4a84f6f4d0b
Timestamp: 1717758292 Timestamp [UCT]: 2024-06-07 11:04:52 Age [y:d:h:m:s]: 00:307:01:28:36
Block: 1038978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219443 RingCT/type: yes/0
Extra: 01d5bbcc4451ed30f236f63f06c5293979b2c3e16325e9e60f453cd4a84f6f4d0b02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cd5e3a1bd3fde465ea586378481499318e81ceffa3b83af183822d7f2d1cc2c 0.600000000000 1507555 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1038988, "vin": [ { "gen": { "height": 1038978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cd5e3a1bd3fde465ea586378481499318e81ceffa3b83af183822d7f2d1cc2c" } } ], "extra": [ 1, 213, 187, 204, 68, 81, 237, 48, 242, 54, 246, 63, 6, 197, 41, 57, 121, 178, 195, 225, 99, 37, 233, 230, 15, 69, 60, 212, 168, 79, 111, 77, 11, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8