Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c117e0c2d2f986f5c3074827bf2bcf04b78236036ba992c331ec2ca88df7d556

Tx prefix hash: 2557f8b0eb9931bb1a69eb3d4efc48c204e5634fffa9d2b79e4bb69c26617a07
Tx public key: 3fa50093e2ad8c2cd2bb19889fb880e93102bfdd5d0e1295feeeafd2d595fd23
Timestamp: 1726616244 Timestamp [UCT]: 2024-09-17 23:37:24 Age [y:d:h:m:s]: 00:132:02:13:31
Block: 1112404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94217 RingCT/type: yes/0
Extra: 013fa50093e2ad8c2cd2bb19889fb880e93102bfdd5d0e1295feeeafd2d595fd2302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f2b919e961833f22d4905cc0c45ca0e319391aced27266d4b05d8625943fffe 0.600000000000 1591713 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": 1112414, "vin": [ { "gen": { "height": 1112404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f2b919e961833f22d4905cc0c45ca0e319391aced27266d4b05d8625943fffe" } } ], "extra": [ 1, 63, 165, 0, 147, 226, 173, 140, 44, 210, 187, 25, 136, 159, 184, 128, 233, 49, 2, 191, 221, 93, 14, 18, 149, 254, 238, 175, 210, 213, 149, 253, 35, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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