Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df7e0ebe590746b011ff4d567d2a0a198253ca92052d343bd45ea9bad64a6523

Tx prefix hash: 4b0c9b7b903d3bda01aaa7c3d249f097cd795e1f306541d3cdd07de3e20d36da
Tx public key: 06c6deee1517d8f2eb97c3dc4a4cc888cca76477f8c55651b5372834f61a20fd
Timestamp: 1727541598 Timestamp [UCT]: 2024-09-28 16:39:58 Age [y:d:h:m:s]: 00:117:18:35:27
Block: 1120085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84156 RingCT/type: yes/0
Extra: 0106c6deee1517d8f2eb97c3dc4a4cc888cca76477f8c55651b5372834f61a20fd02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4baf06f0997ea0fdd4fdfb291c37a9993a614bf82a48900792e700f9eed559f5 0.600000000000 1601874 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": 1120095, "vin": [ { "gen": { "height": 1120085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4baf06f0997ea0fdd4fdfb291c37a9993a614bf82a48900792e700f9eed559f5" } } ], "extra": [ 1, 6, 198, 222, 238, 21, 23, 216, 242, 235, 151, 195, 220, 74, 76, 200, 136, 204, 167, 100, 119, 248, 197, 86, 81, 181, 55, 40, 52, 246, 26, 32, 253, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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