Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c9cd476ada7040fb021d9ebc68298bfb74b642eaeda2bf768766546927ff6d

Tx prefix hash: a96f5c804a229eea24ff1bd85e2e8fff96bcf009f2a9f9f1b228d81784b8cfe3
Tx public key: e7d59f9a0a44e9c564b534029a5c8e820bcdafb650dacf9a584b58b9df263f8f
Timestamp: 1707504053 Timestamp [UCT]: 2024-02-09 18:40:53 Age [y:d:h:m:s]: 01:052:12:08:19
Block: 953949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298563 RingCT/type: yes/0
Extra: 01e7d59f9a0a44e9c564b534029a5c8e820bcdafb650dacf9a584b58b9df263f8f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9038d04c1d8b2b9611f9bf335cbe0809140bb4ba8278c2171bf0470ffc8b4675 0.600000000000 1413221 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": 953959, "vin": [ { "gen": { "height": 953949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9038d04c1d8b2b9611f9bf335cbe0809140bb4ba8278c2171bf0470ffc8b4675" } } ], "extra": [ 1, 231, 213, 159, 154, 10, 68, 233, 197, 100, 181, 52, 2, 154, 92, 142, 130, 11, 205, 175, 182, 80, 218, 207, 154, 88, 75, 88, 185, 223, 38, 63, 143, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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