Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5176a0cb47116138b8dda2fac7aab392b9d6862d154c3fd3bf112259ea212758

Tx prefix hash: 27e4180efb684b43d7e5592c61acf9b7bf827364c5b4958347f0aaf104b11e6c
Tx public key: 1c5301d083fd224436a2d03cbd7d09d9c77dfeae21479f92b01cdf9838b1313f
Timestamp: 1722096409 Timestamp [UCT]: 2024-07-27 16:06:49 Age [y:d:h:m:s]: 00:264:18:07:30
Block: 1074935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189139 RingCT/type: yes/0
Extra: 011c5301d083fd224436a2d03cbd7d09d9c77dfeae21479f92b01cdf9838b1313f02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cac6748b5ff67af896b782026b5f52466a25a5586a538d62a105e5fecec00a29 0.600000000000 1547454 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": 1074945, "vin": [ { "gen": { "height": 1074935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cac6748b5ff67af896b782026b5f52466a25a5586a538d62a105e5fecec00a29" } } ], "extra": [ 1, 28, 83, 1, 208, 131, 253, 34, 68, 54, 162, 208, 60, 189, 125, 9, 217, 199, 125, 254, 174, 33, 71, 159, 146, 176, 28, 223, 152, 56, 177, 49, 63, 2, 17, 0, 0, 0, 11, 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