Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11ce6bb6f89f2793b7f51525d41076b449fec906bf8674af844c18a9e5c55208

Tx prefix hash: 02fd0953c3403b8aa1bbe17a5dbab43839df9a83f49d2a16fcbda761ee59b2af
Tx public key: 757d2ec225047ac6d789ac567b5340b2fcebef7c82dec4b797dd11c01d4dbf34
Timestamp: 1763690163 Timestamp [UCT]: 2025-11-21 01:56:03 Age [y:d:h:m:s]: 00:032:22:10:26
Block: 1416626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23573 RingCT/type: yes/0
Extra: 01757d2ec225047ac6d789ac567b5340b2fcebef7c82dec4b797dd11c01d4dbf3402110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98e39ab915e946c2cf6ca1f2d8e4a5c4b4ef0ad1b1d66d3905c2a78783b451ef 0.600000000000 1905145 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": 1416636, "vin": [ { "gen": { "height": 1416626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98e39ab915e946c2cf6ca1f2d8e4a5c4b4ef0ad1b1d66d3905c2a78783b451ef" } } ], "extra": [ 1, 117, 125, 46, 194, 37, 4, 122, 198, 215, 137, 172, 86, 123, 83, 64, 178, 252, 235, 239, 124, 130, 222, 196, 183, 151, 221, 17, 192, 29, 77, 191, 52, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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