Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65631146fd4ea9a8824d17a3febe242e96ec5cb160faf28d9f8d42b8adfe6600

Tx prefix hash: 10fa85812415391f600e8e297b0c324cb344c5d012e7ce76b3be221dd03c5742
Tx public key: 70d4be8009e2e71d3b3ef26d9fd926616b3873016f3751e51194093503aff23e
Timestamp: 1583837332 Timestamp [UCT]: 2020-03-10 10:48:52 Age [y:d:h:m:s]: 04:290:20:32:14
Block: 79606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103133 RingCT/type: yes/0
Extra: 0170d4be8009e2e71d3b3ef26d9fd926616b3873016f3751e51194093503aff23e0211000000054943cd9f000000000000000000

1 output(s) for total of 334.380215749000 dcy

stealth address amount amount idx
00: 4524715b414cb06758bcf10a37f60e67dd845f9ffa4c93176a08440bf6f4d3f8 334.380215749000 145704 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": 79616, "vin": [ { "gen": { "height": 79606 } } ], "vout": [ { "amount": 334380215749, "target": { "key": "4524715b414cb06758bcf10a37f60e67dd845f9ffa4c93176a08440bf6f4d3f8" } } ], "extra": [ 1, 112, 212, 190, 128, 9, 226, 231, 29, 59, 62, 242, 109, 159, 217, 38, 97, 107, 56, 115, 1, 111, 55, 81, 229, 17, 148, 9, 53, 3, 175, 242, 62, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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