Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2042e67862c80d1b11b0fabf310037c3017ecc20ae52cfd7b1456c6d389a4505

Tx prefix hash: e27ef2898aef8a7d255d41535ff29bfaf39f0c5d7f120bf4c4507d8fc877b8f8
Tx public key: 4d1634d9143d85f092938d2f0ac5c3cb70f7e7f17b54599ffc5553528872d496
Timestamp: 1727935806 Timestamp [UCT]: 2024-10-03 06:10:06 Age [y:d:h:m:s]: 00:112:19:16:17
Block: 1123353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80601 RingCT/type: yes/0
Extra: 014d1634d9143d85f092938d2f0ac5c3cb70f7e7f17b54599ffc5553528872d496021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cbccb4735932e56396dceb7466603cabcaafb91db9b65a5814556284412b7db 0.600000000000 1605886 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": 1123363, "vin": [ { "gen": { "height": 1123353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cbccb4735932e56396dceb7466603cabcaafb91db9b65a5814556284412b7db" } } ], "extra": [ 1, 77, 22, 52, 217, 20, 61, 133, 240, 146, 147, 141, 47, 10, 197, 195, 203, 112, 247, 231, 241, 123, 84, 89, 159, 252, 85, 83, 82, 136, 114, 212, 150, 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