Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de20b0b7962855c81f72fcbccd08cabf4fe2f78d233bf697cb5eccfe7ac96905

Tx prefix hash: c55664a4d7ad19349bef64a026d4c41a22a168a7e9317da99264c6f4cc4780ad
Tx public key: d0c414ebd11077d1ce0e80f13ef8b47c381cee41536fef87cec3e1532e738856
Timestamp: 1737147001 Timestamp [UCT]: 2025-01-17 20:50:01 Age [y:d:h:m:s]: 00:298:02:07:05
Block: 1199563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210540 RingCT/type: yes/0
Extra: 01d0c414ebd11077d1ce0e80f13ef8b47c381cee41536fef87cec3e1532e7388560211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 953c4feb8e9e7b5f41a6a85d1a09ca0383b1cf04698964cea62c5c5e35bd5d84 0.600000000000 1686194 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": 1199573, "vin": [ { "gen": { "height": 1199563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "953c4feb8e9e7b5f41a6a85d1a09ca0383b1cf04698964cea62c5c5e35bd5d84" } } ], "extra": [ 1, 208, 196, 20, 235, 209, 16, 119, 209, 206, 14, 128, 241, 62, 248, 180, 124, 56, 28, 238, 65, 83, 111, 239, 135, 206, 195, 225, 83, 46, 115, 136, 86, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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