Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71a6c6d994d4ea981488b4047d8428aed9cc01df7c5008043382025c1d4ea0cd

Tx prefix hash: 94687e8f1b0db0945bbe8bed2e75e853600c03d903504eb5a13b9da43853c05e
Tx public key: c1435290902335fd4dfe9a3ad3fcbedd429e18234b8773e7d5daa7dc07a9909a
Timestamp: 1762424344 Timestamp [UCT]: 2025-11-06 10:19:04 Age [y:d:h:m:s]: 00:047:12:03:07
Block: 1406133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34022 RingCT/type: yes/0
Extra: 01c1435290902335fd4dfe9a3ad3fcbedd429e18234b8773e7d5daa7dc07a9909a0211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e56fa230df7f11ac12be02183fc4e0610ef998d1d246a0679586fea4b162d441 0.600000000000 1894516 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": 1406143, "vin": [ { "gen": { "height": 1406133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e56fa230df7f11ac12be02183fc4e0610ef998d1d246a0679586fea4b162d441" } } ], "extra": [ 1, 193, 67, 82, 144, 144, 35, 53, 253, 77, 254, 154, 58, 211, 252, 190, 221, 66, 158, 24, 35, 75, 135, 115, 231, 213, 218, 167, 220, 7, 169, 144, 154, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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