Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17c7d7a7c0806a0160ade523b9ab70ad6872d6e1527cb7d9c3120bca28fe4685

Tx prefix hash: eddf66f947e829f304e4805dc309c765b8cb51c60ffa352b7b6834cbdaefb03f
Tx public key: 0fd04031d56cd47d97e35b280d48d55e1842a21d987f647d2a0c443d9b5d0808
Timestamp: 1761651974 Timestamp [UCT]: 2025-10-28 11:46:14 Age [y:d:h:m:s]: 00:024:00:16:55
Block: 1399763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17171 RingCT/type: yes/0
Extra: 010fd04031d56cd47d97e35b280d48d55e1842a21d987f647d2a0c443d9b5d080802110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd124faa672d0eac0e80db08ceb0374b13cf11057b7fbb7f9ddc8e7174fc5405 0.600000000000 1888068 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": 1399773, "vin": [ { "gen": { "height": 1399763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd124faa672d0eac0e80db08ceb0374b13cf11057b7fbb7f9ddc8e7174fc5405" } } ], "extra": [ 1, 15, 208, 64, 49, 213, 108, 212, 125, 151, 227, 91, 40, 13, 72, 213, 94, 24, 66, 162, 29, 152, 127, 100, 125, 42, 12, 68, 61, 155, 93, 8, 8, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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