Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2018e56d5673ab5b9de147729759807c270b3a26b0c463b2e271bf05004402be

Tx prefix hash: db0f2b857b47c22c8a2970908fa2e40c1362a28598178b342818e5d279b5e923
Tx public key: eb2928a031ec6c97a0dbdc090c7d83264e4e3bc8132045d3df8f7225e300f462
Timestamp: 1727756834 Timestamp [UCT]: 2024-10-01 04:27:14 Age [y:d:h:m:s]: 00:191:23:21:38
Block: 1121866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137008 RingCT/type: yes/0
Extra: 01eb2928a031ec6c97a0dbdc090c7d83264e4e3bc8132045d3df8f7225e300f462021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49c88b14402f028b14c821f79af0c6d4a66f494059f8bea62b4a730b5316bea1 0.600000000000 1604223 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": 1121876, "vin": [ { "gen": { "height": 1121866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49c88b14402f028b14c821f79af0c6d4a66f494059f8bea62b4a730b5316bea1" } } ], "extra": [ 1, 235, 41, 40, 160, 49, 236, 108, 151, 160, 219, 220, 9, 12, 125, 131, 38, 78, 78, 59, 200, 19, 32, 69, 211, 223, 143, 114, 37, 227, 0, 244, 98, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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