Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e31f3a6476cb1a48c20766ea9a500d1963d36eea596e91903e81b82ef126c62

Tx prefix hash: d4cdfa44322550ce941b2dba1c1f752946847702f6a0ebe7c337ec26accfe930
Tx public key: 15d72feca1f3a7c1c000fcace58550f5c3c17b6a0e678239da8e6f5d39bf7639
Timestamp: 1759313421 Timestamp [UCT]: 2025-10-01 10:10:21 Age [y:d:h:m:s]: 00:093:16:06:02
Block: 1380361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67087 RingCT/type: yes/0
Extra: 0115d72feca1f3a7c1c000fcace58550f5c3c17b6a0e678239da8e6f5d39bf7639021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ed5e1946276a6eae19d84ef4a5586e00d3766241042edfaef76daa5360bdeb1 0.600000000000 1868472 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": 1380371, "vin": [ { "gen": { "height": 1380361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ed5e1946276a6eae19d84ef4a5586e00d3766241042edfaef76daa5360bdeb1" } } ], "extra": [ 1, 21, 215, 47, 236, 161, 243, 167, 193, 192, 0, 252, 172, 229, 133, 80, 245, 195, 193, 123, 106, 14, 103, 130, 57, 218, 142, 111, 93, 57, 191, 118, 57, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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