Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c84cb5f1a7ce20634379d2a0e6ec08a03f30bbe8f01958ab838529ef52a2068f

Tx prefix hash: 4966484129ed0b3f6cc08a7d094ccd006f37de979e6b47b1b1f9dc7d29f9b5ef
Tx public key: 669405ca08dd6863e24b0d5324128faa25a0b45e0ac625affdcf00f8b60d5e56
Timestamp: 1731003284 Timestamp [UCT]: 2024-11-07 18:14:44 Age [y:d:h:m:s]: 00:144:03:39:02
Block: 1148702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102844 RingCT/type: yes/0
Extra: 01669405ca08dd6863e24b0d5324128faa25a0b45e0ac625affdcf00f8b60d5e5602110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e281a640b804d34d93f59cbea1c85c31ceb775b32f070d9fa9662c3ffc3f96 0.600000000000 1633613 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": 1148712, "vin": [ { "gen": { "height": 1148702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e281a640b804d34d93f59cbea1c85c31ceb775b32f070d9fa9662c3ffc3f96" } } ], "extra": [ 1, 102, 148, 5, 202, 8, 221, 104, 99, 226, 75, 13, 83, 36, 18, 143, 170, 37, 160, 180, 94, 10, 198, 37, 175, 253, 207, 0, 248, 182, 13, 94, 86, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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