Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b79644b6ad1068b5248e168344ffaf68f9ed5b54879e9a2f8a8b86b3e36be6

Tx prefix hash: 4f606940553efa18691c5bd2b1604a9701fec01f3a748e88b275cba940b5e5fe
Tx public key: 4fa074a5bca32cb57e9803799bbec73d95f7b8515c1a6984b28adc7d93315069
Timestamp: 1745516421 Timestamp [UCT]: 2025-04-24 17:40:21 Age [y:d:h:m:s]: 00:200:07:33:06
Block: 1268585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140867 RingCT/type: yes/0
Extra: 014fa074a5bca32cb57e9803799bbec73d95f7b8515c1a6984b28adc7d93315069021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18c9a0fe50b752d2fbcfca6a4bc112803362b25e555165eaf0fa54fd27f7849d 0.600000000000 1755814 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": 1268595, "vin": [ { "gen": { "height": 1268585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18c9a0fe50b752d2fbcfca6a4bc112803362b25e555165eaf0fa54fd27f7849d" } } ], "extra": [ 1, 79, 160, 116, 165, 188, 163, 44, 181, 126, 152, 3, 121, 155, 190, 199, 61, 149, 247, 184, 81, 92, 26, 105, 132, 178, 138, 220, 125, 147, 49, 80, 105, 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