Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42b627099523a123333b962d0118976fa37840c617b2163d112d94b177e397ae

Tx prefix hash: 253d7261f266abd2b3df74c746eb147efa028090c5857cf310db7d0785a6f519
Tx public key: 658bae0cc47ef5135ac397b8ec5d7115a7fdfab29b4ea59a5d16dc96db202dbe
Timestamp: 1718308472 Timestamp [UCT]: 2024-06-13 19:54:32 Age [y:d:h:m:s]: 00:210:16:56:21
Block: 1043536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150782 RingCT/type: yes/0
Extra: 01658bae0cc47ef5135ac397b8ec5d7115a7fdfab29b4ea59a5d16dc96db202dbe0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f2cdc60ef3d4212f60ee6b1477e9da4b1385024e575c18aa4825a6a027ed501 0.600000000000 1512689 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": 1043546, "vin": [ { "gen": { "height": 1043536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f2cdc60ef3d4212f60ee6b1477e9da4b1385024e575c18aa4825a6a027ed501" } } ], "extra": [ 1, 101, 139, 174, 12, 196, 126, 245, 19, 90, 195, 151, 184, 236, 93, 113, 21, 167, 253, 250, 178, 155, 78, 165, 154, 93, 22, 220, 150, 219, 32, 45, 190, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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