Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aa2c037ef038b76c42ea9612f5876e4eb903b79b085e5990615acd528a953cb

Tx prefix hash: 49b3bfe36535a7bae88a1b1da939e436c729095354680030788fa7d884319fbf
Tx public key: a5bf87ac2b682362a08e0e8d294a8bb626a3a2f8aedc2de0f7cc916e43bff4c5
Timestamp: 1765977004 Timestamp [UCT]: 2025-12-17 13:10:04 Age [y:d:h:m:s]: 00:019:09:42:32
Block: 1435586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 13924 RingCT/type: yes/0
Extra: 01a5bf87ac2b682362a08e0e8d294a8bb626a3a2f8aedc2de0f7cc916e43bff4c5

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 922033702033a958dd02e014dd817597b1e37725bdf625f0098135f2bfa1fd50 0.600000000000 1924383 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": 1435596, "vin": [ { "gen": { "height": 1435586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "922033702033a958dd02e014dd817597b1e37725bdf625f0098135f2bfa1fd50" } } ], "extra": [ 1, 165, 191, 135, 172, 43, 104, 35, 98, 160, 142, 14, 141, 41, 74, 139, 182, 38, 163, 162, 248, 174, 220, 45, 224, 247, 204, 145, 110, 67, 191, 244, 197 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8