Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7068604d6aaa607bd3582634dbb18bbae95b2c634a2aae6f58265b2edf0d243

Tx prefix hash: 13ac6a2c6d0311170610c60c87560b2d0a60211dc8c6cb691a20eeca3618a2fa
Tx public key: 5b5ea823b3ee999c4a279347f1c098421285445c28fe46ee7d8384dae9b6e0e9
Timestamp: 1755835953 Timestamp [UCT]: 2025-08-22 04:12:33 Age [y:d:h:m:s]: 00:041:15:30:50
Block: 1351735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29629 RingCT/type: yes/0
Extra: 015b5ea823b3ee999c4a279347f1c098421285445c28fe46ee7d8384dae9b6e0e902110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44dda2aa850b616094cf7ada5dfee787850d70e5f3dbd2a70feb4064da0a3169 0.600000000000 1839692 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": 1351745, "vin": [ { "gen": { "height": 1351735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44dda2aa850b616094cf7ada5dfee787850d70e5f3dbd2a70feb4064da0a3169" } } ], "extra": [ 1, 91, 94, 168, 35, 179, 238, 153, 156, 74, 39, 147, 71, 241, 192, 152, 66, 18, 133, 68, 92, 40, 254, 70, 238, 125, 131, 132, 218, 233, 182, 224, 233, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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