Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b6ad17c0bdc471b11d53936ab3c434dde44f75f43cfa34c05fc0df27998b0c6

Tx prefix hash: 4ed9843a6899e3cddc5972829f312a273e1faf24efa1f09c4b947b6ed23dde9a
Tx public key: 2b354caa2a72e0d7651b66dc7255bbe12eac60026e57481c72fb4afb2a9883c7
Timestamp: 1729722956 Timestamp [UCT]: 2024-10-23 22:35:56 Age [y:d:h:m:s]: 00:090:16:15:30
Block: 1138138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64785 RingCT/type: yes/0
Extra: 012b354caa2a72e0d7651b66dc7255bbe12eac60026e57481c72fb4afb2a9883c70211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8e750cc42edf121329f329bb9bfc9a236350ed866790f20d32799025f4394c5 0.600000000000 1621751 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": 1138148, "vin": [ { "gen": { "height": 1138138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8e750cc42edf121329f329bb9bfc9a236350ed866790f20d32799025f4394c5" } } ], "extra": [ 1, 43, 53, 76, 170, 42, 114, 224, 215, 101, 27, 102, 220, 114, 85, 187, 225, 46, 172, 96, 2, 110, 87, 72, 28, 114, 251, 74, 251, 42, 152, 131, 199, 2, 17, 0, 0, 0, 7, 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