Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56133e89b2a0e70404cf8378fc2d227dbe1eef2c90adb2a47755ce4781e8adb

Tx prefix hash: 8572648f0fce24ff0b9a01f4bec9f690ac2cc0e63c2bb3320e88e9091ee3bef1
Tx public key: 83ab51e9da3309e8a0edcde41317b288fca19268ee53a03afdb5b46002fdabf3
Timestamp: 1693149498 Timestamp [UCT]: 2023-08-27 15:18:18 Age [y:d:h:m:s]: 01:080:08:42:54
Block: 835124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318755 RingCT/type: yes/0
Extra: 0183ab51e9da3309e8a0edcde41317b288fca19268ee53a03afdb5b46002fdabf302110000000a33af99f4000000000000000000

1 output(s) for total of 1.049270807000 dcy

stealth address amount amount idx
00: 8f8255437a3fdbca63b64dc4cbf193ba07080e4c67058193e309e92e22416cb8 1.049270807000 1287662 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": 835134, "vin": [ { "gen": { "height": 835124 } } ], "vout": [ { "amount": 1049270807, "target": { "key": "8f8255437a3fdbca63b64dc4cbf193ba07080e4c67058193e309e92e22416cb8" } } ], "extra": [ 1, 131, 171, 81, 233, 218, 51, 9, 232, 160, 237, 205, 228, 19, 23, 178, 136, 252, 161, 146, 104, 238, 83, 160, 58, 253, 181, 180, 96, 2, 253, 171, 243, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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