Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd780519f63053448c8e90d8bb9789d0f0596b0d97bd41beaf00cc7376e85c6b

Tx prefix hash: 737393d034fb9bd3d6f7e50b4f6dd17505598bb82608def4a55a669796988556
Tx public key: 5b30b50adf5860a2de25ce96bac793f73c550c8fb1431d0f08ab0232e3e2936a
Timestamp: 1766022165 Timestamp [UCT]: 2025-12-18 01:42:45 Age [y:d:h:m:s]: 00:004:18:58:50
Block: 1435966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3430 RingCT/type: yes/0
Extra: 015b30b50adf5860a2de25ce96bac793f73c550c8fb1431d0f08ab0232e3e2936a02110000000ad6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7b7cc5c007b05f9fa6e200c2e30ed0c6ca6a0e911328faab6f18af441ab3329 0.600000000000 1924771 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": 1435976, "vin": [ { "gen": { "height": 1435966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7b7cc5c007b05f9fa6e200c2e30ed0c6ca6a0e911328faab6f18af441ab3329" } } ], "extra": [ 1, 91, 48, 181, 10, 223, 88, 96, 162, 222, 37, 206, 150, 186, 199, 147, 247, 60, 85, 12, 143, 177, 67, 29, 15, 8, 171, 2, 50, 227, 226, 147, 106, 2, 17, 0, 0, 0, 10, 214, 225, 157, 124, 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