Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 580ab97894a5ea9e67b607b34723ae5ef68e176f2821607ca5714143457e4366

Tx prefix hash: cb5b42acbc2577e0fd2444092567dfc9a3b98aea132045d8ad0f0cd947fffb37
Tx public key: df111e83eb40e65e7703d042ac87cd9bddba9d593a6a9d218405ae49f71a06ac
Timestamp: 1754490754 Timestamp [UCT]: 2025-08-06 14:32:34 Age [y:d:h:m:s]: 00:095:09:50:59
Block: 1341522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67198 RingCT/type: yes/0
Extra: 01df111e83eb40e65e7703d042ac87cd9bddba9d593a6a9d218405ae49f71a06ac021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 590cc9bf7d372e63c22c20f892e6d6ec0f50a1321b3160c7855cd71d16043e91 0.600000000000 1829347 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": 1341532, "vin": [ { "gen": { "height": 1341522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "590cc9bf7d372e63c22c20f892e6d6ec0f50a1321b3160c7855cd71d16043e91" } } ], "extra": [ 1, 223, 17, 30, 131, 235, 64, 230, 94, 119, 3, 208, 66, 172, 135, 205, 155, 221, 186, 157, 89, 58, 106, 157, 33, 132, 5, 174, 73, 247, 26, 6, 172, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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