Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86a930abe8a41501a389de23ce63bd65d215acca5b79e0ac33701ba9d6e46212

Tx prefix hash: 5e07f6905766cd8ef11dc4f5ee8ed2b9eb453464c99ec262ddf610ca8c2d2432
Tx public key: a1492ce4f9d953f6efbaf8c906a36a954684640a14ec1d8e08a78660bb5d3c1e
Timestamp: 1741054703 Timestamp [UCT]: 2025-03-04 02:18:23 Age [y:d:h:m:s]: 00:096:05:02:19
Block: 1231641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68831 RingCT/type: yes/0
Extra: 01a1492ce4f9d953f6efbaf8c906a36a954684640a14ec1d8e08a78660bb5d3c1e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72980987f30a78dd258583fb721df0160f888f78a6c05cea240eadb65759ec4e 0.600000000000 1718552 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": 1231651, "vin": [ { "gen": { "height": 1231641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72980987f30a78dd258583fb721df0160f888f78a6c05cea240eadb65759ec4e" } } ], "extra": [ 1, 161, 73, 44, 228, 249, 217, 83, 246, 239, 186, 248, 201, 6, 163, 106, 149, 70, 132, 100, 10, 20, 236, 29, 142, 8, 167, 134, 96, 187, 93, 60, 30, 2, 17, 0, 0, 0, 3, 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