Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c70599fd69955e332f73572a16b51b95f93cf658115f256cc28b97562b45d90

Tx prefix hash: 3c8120dc7f4f34c73dc670b1ed4570df6cbd06d3b602f9a5fc201ab58bfb4176
Tx public key: 8ec0a7c9a293008bdf601983ff2607b029cdbb6a591a9aeca345e037afe1df2d
Timestamp: 1722067240 Timestamp [UCT]: 2024-07-27 08:00:40 Age [y:d:h:m:s]: 01:102:20:19:37
Block: 1074686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331997 RingCT/type: yes/0
Extra: 018ec0a7c9a293008bdf601983ff2607b029cdbb6a591a9aeca345e037afe1df2d02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41e8f55c15804160394eeb50a4dbdb1df2ae2b1aaa9d3e892af5ae532f051332 0.600000000000 1547203 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": 1074696, "vin": [ { "gen": { "height": 1074686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41e8f55c15804160394eeb50a4dbdb1df2ae2b1aaa9d3e892af5ae532f051332" } } ], "extra": [ 1, 142, 192, 167, 201, 162, 147, 0, 139, 223, 96, 25, 131, 255, 38, 7, 176, 41, 205, 187, 106, 89, 26, 154, 236, 163, 69, 224, 55, 175, 225, 223, 45, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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