Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d92e293dc9efcf53fa3529f2037e8d26f5d6a5df62a4688229c210cc3e4dcf

Tx prefix hash: 2c5021478cc9bedc63e640ffba59cecf5db0fec92f6bf96f058c3d22ec7fa5ba
Tx public key: c742d9284fee2cb0327c2eb662ab9fdecf37b11adb1ab694d44a9912d6201d32
Timestamp: 1705293904 Timestamp [UCT]: 2024-01-15 04:45:04 Age [y:d:h:m:s]: 01:130:23:02:16
Block: 935605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354749 RingCT/type: yes/0
Extra: 01c742d9284fee2cb0327c2eb662ab9fdecf37b11adb1ab694d44a9912d6201d320211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 410d9fefb1f0c7148e2b7b349d72af5ad93dfa54b1f97193340faacf544a6142 0.600000000000 1393621 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": 935615, "vin": [ { "gen": { "height": 935605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "410d9fefb1f0c7148e2b7b349d72af5ad93dfa54b1f97193340faacf544a6142" } } ], "extra": [ 1, 199, 66, 217, 40, 79, 238, 44, 176, 50, 124, 46, 182, 98, 171, 159, 222, 207, 55, 177, 26, 219, 26, 182, 148, 212, 74, 153, 18, 214, 32, 29, 50, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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