Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d10a687e956fc500900b8aff4e0a3a7bed689d34c045dbfebf0ba4bfd3a26082

Tx prefix hash: ede68237e8bab205af24edb19672c7d34fa8279cfb9d0519b1f7ba3d1f7cef7d
Tx public key: fcd756603adcc1784209e5e41ae94f44a4ae9fd1a477014b70e6526da3d9b4a3
Timestamp: 1759308573 Timestamp [UCT]: 2025-10-01 08:49:33 Age [y:d:h:m:s]: 00:090:01:00:45
Block: 1380322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64477 RingCT/type: yes/0
Extra: 01fcd756603adcc1784209e5e41ae94f44a4ae9fd1a477014b70e6526da3d9b4a3021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a930d4e28620ddef1ba38945022536ef9fc301833f972fe414213dc104f3b737 0.600000000000 1868433 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": 1380332, "vin": [ { "gen": { "height": 1380322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a930d4e28620ddef1ba38945022536ef9fc301833f972fe414213dc104f3b737" } } ], "extra": [ 1, 252, 215, 86, 96, 58, 220, 193, 120, 66, 9, 229, 228, 26, 233, 79, 68, 164, 174, 159, 209, 164, 119, 1, 75, 112, 230, 82, 109, 163, 217, 180, 163, 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