Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0fa70c54616a58c18410ec9406ca93c54ea8d7cb1f69a13054d11a40a6f4950

Tx prefix hash: 2c1e55b7305881388260afa89e106b503a1a64d0dc75a7395f6f64542d004493
Tx public key: 0ce5d6cd8d99e7f8203e25f7901c6a77af0581e361b9e97479e5e07049d04cfb
Timestamp: 1618261270 Timestamp [UCT]: 2021-04-12 21:01:10 Age [y:d:h:m:s]: 04:029:04:31:59
Block: 238493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1041769 RingCT/type: yes/0
Extra: 010ce5d6cd8d99e7f8203e25f7901c6a77af0581e361b9e97479e5e07049d04cfb02110000009a6eb9c26a000000000000000000

1 output(s) for total of 99.492805041000 dcy

stealth address amount amount idx
00: 364bc4b17900107d2d57a4c8f1fc1f7c532fa9239fbaea41216e3a31f247be4c 99.492805041000 496601 of 0

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": 238503, "vin": [ { "gen": { "height": 238493 } } ], "vout": [ { "amount": 99492805041, "target": { "key": "364bc4b17900107d2d57a4c8f1fc1f7c532fa9239fbaea41216e3a31f247be4c" } } ], "extra": [ 1, 12, 229, 214, 205, 141, 153, 231, 248, 32, 62, 37, 247, 144, 28, 106, 119, 175, 5, 129, 227, 97, 185, 233, 116, 121, 229, 224, 112, 73, 208, 76, 251, 2, 17, 0, 0, 0, 154, 110, 185, 194, 106, 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