Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f83e82e14aacc5488dcec68bb6b7ec876e2ce157b5ba4406ba9d992aa2e18196

Tx prefix hash: 3f153202404b2571383896419821f256b190ac4a547cdb66abf0e272bdc199de
Tx public key: 99518e4e8e3b0b765cdb1a49cdbae96d36d7efd78243317dcd8183d54303482b
Timestamp: 1720068889 Timestamp [UCT]: 2024-07-04 04:54:49 Age [y:d:h:m:s]: 00:317:02:55:59
Block: 1058117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226630 RingCT/type: yes/0
Extra: 0199518e4e8e3b0b765cdb1a49cdbae96d36d7efd78243317dcd8183d54303482b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a31fa20580e49f2d0d3efde379d202d64474b1cb20a9bcd7e1fd5389f3bcb15c 0.600000000000 1528566 of 15

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": 1058127, "vin": [ { "gen": { "height": 1058117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a31fa20580e49f2d0d3efde379d202d64474b1cb20a9bcd7e1fd5389f3bcb15c" } } ], "extra": [ 1, 153, 81, 142, 78, 142, 59, 11, 118, 92, 219, 26, 73, 205, 186, 233, 109, 54, 215, 239, 215, 130, 67, 49, 125, 205, 129, 131, 213, 67, 3, 72, 43, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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