Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 347c01c2c3fc1b82c39ecb6a503c98ee866b27978b3ff14d48629d8de0f92853

Tx prefix hash: 0c41939a5c46bd2dfcced01917c20eed66108b360c4360b5920a9f3b0f25a449
Tx public key: d2cbe990c2a74a96dddac6bd29448b9ad2eb98ba9ffa546923508690f9652e96
Timestamp: 1582968156 Timestamp [UCT]: 2020-02-29 09:22:36 Age [y:d:h:m:s]: 04:320:00:50:58
Block: 73858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122536 RingCT/type: yes/0
Extra: 01d2cbe990c2a74a96dddac6bd29448b9ad2eb98ba9ffa546923508690f9652e960211000002937adf42d3000000000000000000

1 output(s) for total of 349.364348877000 dcy

stealth address amount amount idx
00: 7e4618377e8e7db8e76e65ec4f1f00c2c19e37636dea181efd35f77e291fb0d7 349.364348877000 136480 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": 73868, "vin": [ { "gen": { "height": 73858 } } ], "vout": [ { "amount": 349364348877, "target": { "key": "7e4618377e8e7db8e76e65ec4f1f00c2c19e37636dea181efd35f77e291fb0d7" } } ], "extra": [ 1, 210, 203, 233, 144, 194, 167, 74, 150, 221, 218, 198, 189, 41, 68, 139, 154, 210, 235, 152, 186, 159, 250, 84, 105, 35, 80, 134, 144, 249, 101, 46, 150, 2, 17, 0, 0, 2, 147, 122, 223, 66, 211, 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