Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c29796c9bdb7415b6df80bc56dab423d30087c6cb0f5bbdbf91462fd41946f0d

Tx prefix hash: 01180eb9d3b47f93b8274b42b8ce986a4537f33ca55de8e3fded42950cb22bfc
Tx public key: d1a5cd65d1dffbfd4090c022c59448c756341cf1f7c8a03cc87fc5d0a6f60411
Timestamp: 1725312366 Timestamp [UCT]: 2024-09-02 21:26:06 Age [y:d:h:m:s]: 00:226:08:57:24
Block: 1101600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161639 RingCT/type: yes/0
Extra: 01d1a5cd65d1dffbfd4090c022c59448c756341cf1f7c8a03cc87fc5d0a6f60411021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87ad733f3968c55ff369d3a49339a5211ed5a9261ba2d2bfdadf9b75e1883a2b 0.600000000000 1577711 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": 1101610, "vin": [ { "gen": { "height": 1101600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87ad733f3968c55ff369d3a49339a5211ed5a9261ba2d2bfdadf9b75e1883a2b" } } ], "extra": [ 1, 209, 165, 205, 101, 209, 223, 251, 253, 64, 144, 192, 34, 197, 148, 72, 199, 86, 52, 28, 241, 247, 200, 160, 60, 200, 127, 197, 208, 166, 246, 4, 17, 2, 17, 0, 0, 0, 3, 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