Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e051dfec88cc27dc5c4dfca9247e230e17ad50c28335267b5adee6b7e7f4b1d1

Tx prefix hash: 2c9b8cd6b553f657301bdc65213b9b301ae629ab1f617df61caeb910af449e82
Tx public key: cac8e5d37d5176e37216dc691ccaf6957ab3ed46e148698ed89375c940adcef7
Timestamp: 1727916330 Timestamp [UCT]: 2024-10-03 00:45:30 Age [y:d:h:m:s]: 01:036:19:05:02
Block: 1123189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284675 RingCT/type: yes/0
Extra: 01cac8e5d37d5176e37216dc691ccaf6957ab3ed46e148698ed89375c940adcef702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb87ed4dc75511b132568df58ae14e95073e7e7326e28f3f7f6c9e4c1b4b6952 0.600000000000 1605722 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": 1123199, "vin": [ { "gen": { "height": 1123189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb87ed4dc75511b132568df58ae14e95073e7e7326e28f3f7f6c9e4c1b4b6952" } } ], "extra": [ 1, 202, 200, 229, 211, 125, 81, 118, 227, 114, 22, 220, 105, 28, 202, 246, 149, 122, 179, 237, 70, 225, 72, 105, 142, 216, 147, 117, 201, 64, 173, 206, 247, 2, 17, 0, 0, 0, 3, 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