Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e39488c24ffcc244555360720eefea1b742f025579c9d5822d224b7f7250051c

Tx prefix hash: 0b8865db0e5e4de268243d4c1650614a0a5942a803660b0b16966418d909f3e2
Tx public key: 0698273f3b53b643b9e8aa23d70bb398efe7d1c8faa3f1977580386d4d757fb9
Timestamp: 1757297823 Timestamp [UCT]: 2025-09-08 02:17:03 Age [y:d:h:m:s]: 00:147:02:28:01
Block: 1363758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105051 RingCT/type: yes/0
Extra: 010698273f3b53b643b9e8aa23d70bb398efe7d1c8faa3f1977580386d4d757fb9021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f5442bf940b529ad5494195997d5acb835e31b5568cc99a5d807cf8d91ee72a 0.600000000000 1851797 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": 1363768, "vin": [ { "gen": { "height": 1363758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f5442bf940b529ad5494195997d5acb835e31b5568cc99a5d807cf8d91ee72a" } } ], "extra": [ 1, 6, 152, 39, 63, 59, 83, 182, 67, 185, 232, 170, 35, 215, 11, 179, 152, 239, 231, 209, 200, 250, 163, 241, 151, 117, 128, 56, 109, 77, 117, 127, 185, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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