Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c481f52ee60fea822d47ec8393caa4c64d9c505c737fd42e491c1b47855e5dc2

Tx prefix hash: 1c18666e3eadd21abdac20a90e02693c009697ad878fee731f62206ef43d4f8a
Tx public key: d9057dc1b5329cd983eaf9d8ac00c524f896fbe801f8cb410587a52521735e23
Timestamp: 1714166918 Timestamp [UCT]: 2024-04-26 21:28:38 Age [y:d:h:m:s]: 01:052:09:39:46
Block: 1009192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298303 RingCT/type: yes/0
Extra: 01d9057dc1b5329cd983eaf9d8ac00c524f896fbe801f8cb410587a52521735e230211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dde547ae40024fac3c657c93e7ccdb09804bc29a94ef34ac0a05f8d250c9f4dc 0.600000000000 1470796 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": 1009202, "vin": [ { "gen": { "height": 1009192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dde547ae40024fac3c657c93e7ccdb09804bc29a94ef34ac0a05f8d250c9f4dc" } } ], "extra": [ 1, 217, 5, 125, 193, 181, 50, 156, 217, 131, 234, 249, 216, 172, 0, 197, 36, 248, 150, 251, 232, 1, 248, 203, 65, 5, 135, 165, 37, 33, 115, 94, 35, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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