Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f793cbd5bdb436fb4b64e76ea7b79d992710c48532cceaaad5c12f60c3ce64c

Tx prefix hash: d290be92f868a8d4be198192d3a1a7b4ef6d8001126bd48f0f0f8df27c2fd6d8
Tx public key: 1b9c55b0cbe2a729ae23be1ba36ff3334178f0365a08f1ebd215627bd396dd5c
Timestamp: 1696743058 Timestamp [UCT]: 2023-10-08 05:30:58 Age [y:d:h:m:s]: 01:172:18:21:28
Block: 864951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384503 RingCT/type: yes/0
Extra: 011b9c55b0cbe2a729ae23be1ba36ff3334178f0365a08f1ebd215627bd396dd5c0211000000044b8f5122000000000000000000

1 output(s) for total of 0.835715224000 dcy

stealth address amount amount idx
00: 10ecaf6a9030299a8167c04888aae01ef7e4123a0056975d461f57b34b0d97dc 0.835715224000 1319477 of 0

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": 864961, "vin": [ { "gen": { "height": 864951 } } ], "vout": [ { "amount": 835715224, "target": { "key": "10ecaf6a9030299a8167c04888aae01ef7e4123a0056975d461f57b34b0d97dc" } } ], "extra": [ 1, 27, 156, 85, 176, 203, 226, 167, 41, 174, 35, 190, 27, 163, 111, 243, 51, 65, 120, 240, 54, 90, 8, 241, 235, 210, 21, 98, 123, 211, 150, 221, 92, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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