Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f2cd2ffdb82afe03ba4a55499375a776e706f178bbfecd9cb3da969ec648b0c

Tx prefix hash: e107f4e992a01891b9aeff3e5a04cfbd2f4298eb2a329e21128c90667b7f1488
Tx public key: b61d4c023cb9dc30b1ccf28d799912e5edcb095748574c9cc49aa5f48714c580
Timestamp: 1703893317 Timestamp [UCT]: 2023-12-29 23:41:57 Age [y:d:h:m:s]: 01:031:00:44:35
Block: 924017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283269 RingCT/type: yes/0
Extra: 01b61d4c023cb9dc30b1ccf28d799912e5edcb095748574c9cc49aa5f48714c58002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b87176efafdbfb27f6a1f596e25e7187ca2efbae594a777ceb363f34cad7ccec 0.600000000000 1381759 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": 924027, "vin": [ { "gen": { "height": 924017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b87176efafdbfb27f6a1f596e25e7187ca2efbae594a777ceb363f34cad7ccec" } } ], "extra": [ 1, 182, 29, 76, 2, 60, 185, 220, 48, 177, 204, 242, 141, 121, 153, 18, 229, 237, 203, 9, 87, 72, 87, 76, 156, 196, 154, 165, 244, 135, 20, 197, 128, 2, 17, 0, 0, 0, 2, 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