Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b08a4f221c56a2c5ac64101bbdca53f52393ce3497f5d448c388dfec6b0d2c59

Tx prefix hash: bcd548fae8b4a0c5331250b07575dfd5d9561139a7de66ad8a8edb00e4d9dc91
Tx public key: 8e6d9b6d731dd118237c98d0011c0348c386310091721d1dad1b17bafc8308f1
Timestamp: 1752008023 Timestamp [UCT]: 2025-07-08 20:53:43 Age [y:d:h:m:s]: 00:130:07:37:22
Block: 1321552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91587 RingCT/type: yes/0
Extra: 018e6d9b6d731dd118237c98d0011c0348c386310091721d1dad1b17bafc8308f10211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d6e8b5c380ae9ab20af2f9dfc793b47ff36a7670a383322012991c746f7ba1c 0.600000000000 1809259 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": 1321562, "vin": [ { "gen": { "height": 1321552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d6e8b5c380ae9ab20af2f9dfc793b47ff36a7670a383322012991c746f7ba1c" } } ], "extra": [ 1, 142, 109, 155, 109, 115, 29, 209, 24, 35, 124, 152, 208, 1, 28, 3, 72, 195, 134, 49, 0, 145, 114, 29, 29, 173, 27, 23, 186, 252, 131, 8, 241, 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