Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b0e3a71a7ff4c591d3259853cfcedef6a51f709e0862eccbb9f8384e9b518f0

Tx prefix hash: 51697dafa1507c04ade9c86d8318a2cf6dd3bb751f1b9dea5a89cfa49de03f99
Tx public key: 81fdc30954a449cbfcf402e664f5a5cc4c681de74b7addd956f04a34dcb03e28
Timestamp: 1756966032 Timestamp [UCT]: 2025-09-04 06:07:12 Age [y:d:h:m:s]: 00:109:04:51:32
Block: 1360984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78118 RingCT/type: yes/0
Extra: 0181fdc30954a449cbfcf402e664f5a5cc4c681de74b7addd956f04a34dcb03e28021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 828366c5cdc7bbc9c3f19b72bc2526d177564a3628698556734a8b5e120aca96 0.600000000000 1848997 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": 1360994, "vin": [ { "gen": { "height": 1360984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "828366c5cdc7bbc9c3f19b72bc2526d177564a3628698556734a8b5e120aca96" } } ], "extra": [ 1, 129, 253, 195, 9, 84, 164, 73, 203, 252, 244, 2, 230, 100, 245, 165, 204, 76, 104, 29, 231, 75, 122, 221, 217, 86, 240, 74, 52, 220, 176, 62, 40, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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