Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53080322ad4de3adac0a367850fb045c23150ba826b424715b3150ced404db01

Tx prefix hash: dd46ed27a4c9834a7b42d62566a1fd9bc138e4e34cb08d4b4e5bf6470a5e3a35
Tx public key: 3ac77c9ff448037dcdf6162c7662d1cf84fb66074b574a85e43cba217ba54260
Timestamp: 1634529867 Timestamp [UCT]: 2021-10-18 04:04:27 Age [y:d:h:m:s]: 03:117:18:44:53
Block: 355345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 861900 RingCT/type: yes/0
Extra: 013ac77c9ff448037dcdf6162c7662d1cf84fb66074b574a85e43cba217ba5426002110000000336fe6557000000000000000000

1 output(s) for total of 40.794581171000 dcy

stealth address amount amount idx
00: 81c30606fcfaf01bdf7a1da0fb91aa8360b1c47e00a9e3b01dad7f1c719d8fe1 40.794581171000 725503 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": 355355, "vin": [ { "gen": { "height": 355345 } } ], "vout": [ { "amount": 40794581171, "target": { "key": "81c30606fcfaf01bdf7a1da0fb91aa8360b1c47e00a9e3b01dad7f1c719d8fe1" } } ], "extra": [ 1, 58, 199, 124, 159, 244, 72, 3, 125, 205, 246, 22, 44, 118, 98, 209, 207, 132, 251, 102, 7, 75, 87, 74, 133, 228, 60, 186, 33, 123, 165, 66, 96, 2, 17, 0, 0, 0, 3, 54, 254, 101, 87, 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