Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b8ec889667035a45f48318256bfd79f0c77a695463af77b4af5c6b7e5d3ab53

Tx prefix hash: 0154942a02584ebd26d6596310d31c6de349fe0edfa03e347f2d42745ac85f6f
Tx public key: 1d70e4f33bd07c6a7ccfe53fb92f9d3fbb5dfa293247c2cd35982782684d12a8
Timestamp: 1732060584 Timestamp [UCT]: 2024-11-19 23:56:24 Age [y:d:h:m:s]: 00:206:10:14:30
Block: 1157454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147323 RingCT/type: yes/0
Extra: 011d70e4f33bd07c6a7ccfe53fb92f9d3fbb5dfa293247c2cd35982782684d12a8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bd7cd047394d0be2189442f392dcc50bc09dcb8274fbc15be8c1b2707d53e21 0.600000000000 1643077 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": 1157464, "vin": [ { "gen": { "height": 1157454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bd7cd047394d0be2189442f392dcc50bc09dcb8274fbc15be8c1b2707d53e21" } } ], "extra": [ 1, 29, 112, 228, 243, 59, 208, 124, 106, 124, 207, 229, 63, 185, 47, 157, 63, 187, 93, 250, 41, 50, 71, 194, 205, 53, 152, 39, 130, 104, 77, 18, 168, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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