Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 153d86ab0cc315b51ef3e67168bf801b02591dcd525d236125789880b891781b

Tx prefix hash: 0507bfed346aad24d0e19fab2b71d8d375fd39ae021e7ea7074d1b0bb5632167
Tx public key: 54caf751735c1e289a8d36a7fec92f2f41637df56de016de34bd5c2689c0920a
Timestamp: 1580734791 Timestamp [UCT]: 2020-02-03 12:59:51 Age [y:d:h:m:s]: 05:073:11:34:45
Block: 57888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204458 RingCT/type: yes/0
Extra: 0154caf751735c1e289a8d36a7fec92f2f41637df56de016de34bd5c2689c0920a021100000043e88dac00000000000000000000

1 output(s) for total of 394.633407056000 dcy

stealth address amount amount idx
00: fdd32a44f41c0c786480e7d2aa86535499c41145c15cac291a50ee6a9a23b8f6 394.633407056000 107055 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": 57898, "vin": [ { "gen": { "height": 57888 } } ], "vout": [ { "amount": 394633407056, "target": { "key": "fdd32a44f41c0c786480e7d2aa86535499c41145c15cac291a50ee6a9a23b8f6" } } ], "extra": [ 1, 84, 202, 247, 81, 115, 92, 30, 40, 154, 141, 54, 167, 254, 201, 47, 47, 65, 99, 125, 245, 109, 224, 22, 222, 52, 189, 92, 38, 137, 192, 146, 10, 2, 17, 0, 0, 0, 67, 232, 141, 172, 0, 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