Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aad4d45c5f0a5ea8a29dd1165d300ec92e3c9301aa05b8038ce9a89a005ea16

Tx prefix hash: 8d562659fb06a998cf0302542ef6872468fb57639ec1dd88e252936710768d93
Tx public key: 168bc8f94fd37b33d6dbb4ad6c0374448ca0596c8d78aba5a55c8be29512c417
Timestamp: 1708999504 Timestamp [UCT]: 2024-02-27 02:05:04 Age [y:d:h:m:s]: 01:063:01:33:17
Block: 966367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306099 RingCT/type: yes/0
Extra: 01168bc8f94fd37b33d6dbb4ad6c0374448ca0596c8d78aba5a55c8be29512c41702110000001252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68e6a3f47b5e2b8f202417bd76e224e426a2dc147bfe4c16dc60c0b7a9886f05 0.600000000000 1426124 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": 966377, "vin": [ { "gen": { "height": 966367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68e6a3f47b5e2b8f202417bd76e224e426a2dc147bfe4c16dc60c0b7a9886f05" } } ], "extra": [ 1, 22, 139, 200, 249, 79, 211, 123, 51, 214, 219, 180, 173, 108, 3, 116, 68, 140, 160, 89, 108, 141, 120, 171, 165, 165, 92, 139, 226, 149, 18, 196, 23, 2, 17, 0, 0, 0, 18, 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