Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 531a37d8a04798d1ece7174cc4e4ceaba48e70c9a5e657451a4694924ba02c75

Tx prefix hash: b90646c275c9dd5adcca7e8ae8e84f1381eaa2564a64a9ef1137f0cc0057e850
Tx public key: 224e6366d76c89c8f27417c6734f2e194c8be8222381887c8a14b711efa7c829
Timestamp: 1764629475 Timestamp [UCT]: 2025-12-01 22:51:15 Age [y:d:h:m:s]: 00:022:05:36:08
Block: 1424428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15911 RingCT/type: yes/0
Extra: 01224e6366d76c89c8f27417c6734f2e194c8be8222381887c8a14b711efa7c82902110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d14b38eb3f85311e19bc591c8f89a346e679f452c15915bce56e0c96cec91c4 0.600000000000 1913059 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": 1424438, "vin": [ { "gen": { "height": 1424428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d14b38eb3f85311e19bc591c8f89a346e679f452c15915bce56e0c96cec91c4" } } ], "extra": [ 1, 34, 78, 99, 102, 215, 108, 137, 200, 242, 116, 23, 198, 115, 79, 46, 25, 76, 139, 232, 34, 35, 129, 136, 124, 138, 20, 183, 17, 239, 167, 200, 41, 2, 17, 0, 0, 0, 1, 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