Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7416d89a891255a0101c9f29b19a102577ba405c7c04f1c2635785398a00ab4

Tx prefix hash: 877688a9fd7b53d353811ed30c912bcd173ad7434f73e13e6d461e5050036d84
Tx public key: 93acf082d918b4eba7adb8e33abf17dd963cd385438c98256bab8b7e359335fe
Timestamp: 1715439212 Timestamp [UCT]: 2024-05-11 14:53:32 Age [y:d:h:m:s]: 00:325:06:22:31
Block: 1019771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232455 RingCT/type: yes/0
Extra: 0193acf082d918b4eba7adb8e33abf17dd963cd385438c98256bab8b7e359335fe02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93e8c2540138a822f677aeea4d9fd0781cbdf325e4d2a19887fde51f4d27ffc8 0.600000000000 1483812 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": 1019781, "vin": [ { "gen": { "height": 1019771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93e8c2540138a822f677aeea4d9fd0781cbdf325e4d2a19887fde51f4d27ffc8" } } ], "extra": [ 1, 147, 172, 240, 130, 217, 24, 180, 235, 167, 173, 184, 227, 58, 191, 23, 221, 150, 60, 211, 133, 67, 140, 152, 37, 107, 171, 139, 126, 53, 147, 53, 254, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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