Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12adb7c19ccefbd9a70608ab7c9be9b87ab263890f5cc585ce8a5a9eff1d2ae4

Tx prefix hash: 24dabcf22d0426320da68287727973e3d67dad864d39d59f016f52d7d9153d4f
Tx public key: b1280ea61139c48637978de51d3fa135f8ca27f52c36f3d3d1098508100a278d
Timestamp: 1583347648 Timestamp [UCT]: 2020-03-04 18:47:28 Age [y:d:h:m:s]: 04:317:08:14:01
Block: 76516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121088 RingCT/type: yes/0
Extra: 01b1280ea61139c48637978de51d3fa135f8ca27f52c36f3d3d1098508100a278d02110000003b7adf42d3000000000000000000

1 output(s) for total of 342.350939285000 dcy

stealth address amount amount idx
00: 8d60971604625e0e9b9b28e7e94f81c00e52d5822cbac0a2a37260eb9e2772d0 342.350939285000 140786 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": 76526, "vin": [ { "gen": { "height": 76516 } } ], "vout": [ { "amount": 342350939285, "target": { "key": "8d60971604625e0e9b9b28e7e94f81c00e52d5822cbac0a2a37260eb9e2772d0" } } ], "extra": [ 1, 177, 40, 14, 166, 17, 57, 196, 134, 55, 151, 141, 229, 29, 63, 161, 53, 248, 202, 39, 245, 44, 54, 243, 211, 209, 9, 133, 8, 16, 10, 39, 141, 2, 17, 0, 0, 0, 59, 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