Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee2b36d112de6976934cc457d28f3f662e0f3ab909adf75b1701d10cfa0b0bf3

Tx prefix hash: f769ea57167b0622f409cb10492c5a14f0fec1c3dd828c013f81d531088245a5
Tx public key: be6174830f654b932857c0e4ba5dde843d7fc8dcd2d0cbd3fefda5e37ebdb6d9
Timestamp: 1722094261 Timestamp [UCT]: 2024-07-27 15:31:01 Age [y:d:h:m:s]: 00:255:02:53:53
Block: 1074916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182239 RingCT/type: yes/0
Extra: 01be6174830f654b932857c0e4ba5dde843d7fc8dcd2d0cbd3fefda5e37ebdb6d9021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec08b87caf9dc1c44ea755e3bf6c0d588f78d4cba12b76ed8d7dca1bfbe733b4 0.600000000000 1547435 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": 1074926, "vin": [ { "gen": { "height": 1074916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec08b87caf9dc1c44ea755e3bf6c0d588f78d4cba12b76ed8d7dca1bfbe733b4" } } ], "extra": [ 1, 190, 97, 116, 131, 15, 101, 75, 147, 40, 87, 192, 228, 186, 93, 222, 132, 61, 127, 200, 220, 210, 208, 203, 211, 254, 253, 165, 227, 126, 189, 182, 217, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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