Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd0054381d8a64b24d1f0438629099236d63dc3e950b80c812e2adf611815e31

Tx prefix hash: 784242057c261637a7148c6404b424b0cb31d3c04666f8c014cd25abbaeb39d4
Tx public key: 0ac44987bed1433ce2c86a52e0aacd56f6195b5eae020b1547ce20fa81eb2a9e
Timestamp: 1752540277 Timestamp [UCT]: 2025-07-15 00:44:37 Age [y:d:h:m:s]: 00:199:01:49:55
Block: 1325674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140937 RingCT/type: yes/0
Extra: 010ac44987bed1433ce2c86a52e0aacd56f6195b5eae020b1547ce20fa81eb2a9e02110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa0ae851be7d9145dedd7d67e7f5326555df285a540e4a3d9ce1ed8ac17a56ea 0.600000000000 1813421 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": 1325684, "vin": [ { "gen": { "height": 1325674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa0ae851be7d9145dedd7d67e7f5326555df285a540e4a3d9ce1ed8ac17a56ea" } } ], "extra": [ 1, 10, 196, 73, 135, 190, 209, 67, 60, 226, 200, 106, 82, 224, 170, 205, 86, 246, 25, 91, 94, 174, 2, 11, 21, 71, 206, 32, 250, 129, 235, 42, 158, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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