Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85c6c65b45a1aa44287c4c77f689a767dec063687e6f32b660873d0abb0f5fda

Tx prefix hash: 9c27aa6480a3e80957d18de7e9ee192e12e81fb16cb9337d54a48257e926f9a5
Tx public key: f81fa0b6f77346aa8b4099eff0a1f881eabf5dc3057bc9424aeccaf3f5127881
Timestamp: 1763089007 Timestamp [UCT]: 2025-11-14 02:56:47 Age [y:d:h:m:s]: 00:014:06:30:26
Block: 1411665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10216 RingCT/type: yes/0
Extra: 01f81fa0b6f77346aa8b4099eff0a1f881eabf5dc3057bc9424aeccaf3f5127881021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a2f50cdad85b1d55033ea547637edf4e470788b78216b1ad5659e8ac2c5d8d5 0.600000000000 1900128 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": 1411675, "vin": [ { "gen": { "height": 1411665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2f50cdad85b1d55033ea547637edf4e470788b78216b1ad5659e8ac2c5d8d5" } } ], "extra": [ 1, 248, 31, 160, 182, 247, 115, 70, 170, 139, 64, 153, 239, 240, 161, 248, 129, 234, 191, 93, 195, 5, 123, 201, 66, 74, 236, 202, 243, 245, 18, 120, 129, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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