Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfbbe660e5f576cd962ceef25afda39fdcfea1b0ce548b86cba3d1d67a491587

Tx prefix hash: 20ee59a21590e7bfe2276b1695d3c5d8a4ccc9fad763dbf904c872eee7ce77a5
Tx public key: 4b64c2cb7090a2d9d0a5ea970de65399c4f33b0c6bb529426494b868fb1b5ccf
Timestamp: 1703024355 Timestamp [UCT]: 2023-12-19 22:19:15 Age [y:d:h:m:s]: 01:328:02:19:08
Block: 916823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493341 RingCT/type: yes/0
Extra: 014b64c2cb7090a2d9d0a5ea970de65399c4f33b0c6bb529426494b868fb1b5ccf021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9d7008031e73e184ff1a346dc489a630780bfb130101c843c3d0aee9d301ad0 0.600000000000 1374383 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": 916833, "vin": [ { "gen": { "height": 916823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9d7008031e73e184ff1a346dc489a630780bfb130101c843c3d0aee9d301ad0" } } ], "extra": [ 1, 75, 100, 194, 203, 112, 144, 162, 217, 208, 165, 234, 151, 13, 230, 83, 153, 196, 243, 59, 12, 107, 181, 41, 66, 100, 148, 184, 104, 251, 27, 92, 207, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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