Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ab319da452f11c41b8f4f731d0bcbbd0fd353ef36d0523868db4ed794b4cc0

Tx prefix hash: fe159986ed764e6bc6fc461f1e358dbdb37e1fa940da11a826772160d395eb29
Tx public key: 696e4a1b945b7bd3c95e56c28cb26093a30d9483f762f8a1538ce0b922021d0f
Timestamp: 1734254372 Timestamp [UCT]: 2024-12-15 09:19:32 Age [y:d:h:m:s]: 00:100:17:25:37
Block: 1175642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71742 RingCT/type: yes/0
Extra: 01696e4a1b945b7bd3c95e56c28cb26093a30d9483f762f8a1538ce0b922021d0f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c5d327b7d45629d51c1613b72f73d6ad6b0c19816f9a1d712145c8cc6abcd37 0.600000000000 1661951 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": 1175652, "vin": [ { "gen": { "height": 1175642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c5d327b7d45629d51c1613b72f73d6ad6b0c19816f9a1d712145c8cc6abcd37" } } ], "extra": [ 1, 105, 110, 74, 27, 148, 91, 123, 211, 201, 94, 86, 194, 140, 178, 96, 147, 163, 13, 148, 131, 247, 98, 248, 161, 83, 140, 224, 185, 34, 2, 29, 15, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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