Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f47b7c89b4389a4de8ce70c48c956876ff7fcc5e15a8847b2ee70e0dc664ccf

Tx prefix hash: d985e0b1eb5d93b21848b5d566291c7a6e423944941b0b24b855e6d73c7eb44f
Tx public key: ced1cf6d31244bb6e03bbff0c3ef419e1395d41738506ef388f6ed0b00a46ae2
Timestamp: 1760454938 Timestamp [UCT]: 2025-10-14 15:15:38 Age [y:d:h:m:s]: 00:069:16:24:10
Block: 1389826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49891 RingCT/type: yes/0
Extra: 01ced1cf6d31244bb6e03bbff0c3ef419e1395d41738506ef388f6ed0b00a46ae20211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53764f4390eef1a7b4277ec197119e2b73b1f95c5047bb82242d554c92d22f89 0.600000000000 1878055 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": 1389836, "vin": [ { "gen": { "height": 1389826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53764f4390eef1a7b4277ec197119e2b73b1f95c5047bb82242d554c92d22f89" } } ], "extra": [ 1, 206, 209, 207, 109, 49, 36, 75, 182, 224, 59, 191, 240, 195, 239, 65, 158, 19, 149, 212, 23, 56, 80, 110, 243, 136, 246, 237, 11, 0, 164, 106, 226, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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