Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63641521f3ffaf0d8a109339cafba260f3af4288d94897397a0a2c11e22186d6

Tx prefix hash: bc2f6f0eee61dba29bee6241db8d15ee69793bc880cb251ff189aaedfcf12114
Tx public key: 9f3ed6f0b98a97e4ce6adc6c6707f64fd34f67360706174d646da6d025f827ba
Timestamp: 1760409172 Timestamp [UCT]: 2025-10-14 02:32:52 Age [y:d:h:m:s]: 00:111:11:19:58
Block: 1389472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79618 RingCT/type: yes/0
Extra: 019f3ed6f0b98a97e4ce6adc6c6707f64fd34f67360706174d646da6d025f827ba0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcc1f239769005c8f2ae6b4ea854c0c729abaafc53a78f41047d820e5931560c 0.600000000000 1877701 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": 1389482, "vin": [ { "gen": { "height": 1389472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcc1f239769005c8f2ae6b4ea854c0c729abaafc53a78f41047d820e5931560c" } } ], "extra": [ 1, 159, 62, 214, 240, 185, 138, 151, 228, 206, 106, 220, 108, 103, 7, 246, 79, 211, 79, 103, 54, 7, 6, 23, 77, 100, 109, 166, 208, 37, 248, 39, 186, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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