Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c67b06c771227330c6db32795f864b23b089e5d644a7db8344d5cbc6907764f

Tx prefix hash: fc5106d9a0e9254d53c06476c8d383af6dcc68d9ebba70dcaf337d09b8ce262c
Tx public key: ed6d3a5146ae1a969b3894b23ac88be45c53e2d02a755879e84d8f8791f6c114
Timestamp: 1634740448 Timestamp [UTC]: 2021-10-20 14:34:08 Age [y:d:h:m:s]: 05:033:21:37:15
Block: 356858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1326636 RingCT/type: yes/0
Extra: 01ed6d3a5146ae1a969b3894b23ac88be45c53e2d02a755879e84d8f8791f6c11402110000000c36fe6557000000000000000000

1 output(s) for total of 0.040327931972 xmr

stealth address amount amount idx tag
00: 41ce92b5d03dfb1a71abaa716683df9de3d4968cc161ccb093b706c4f4137d7b 0.040327931972 727912 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 dinastycoin-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": 356868, "vin": [ { "gen": { "height": 356858 } } ], "vout": [ { "amount": 40327931972, "target": { "key": "41ce92b5d03dfb1a71abaa716683df9de3d4968cc161ccb093b706c4f4137d7b" } } ], "extra": [ 1, 237, 109, 58, 81, 70, 174, 26, 150, 155, 56, 148, 178, 58, 200, 139, 228, 92, 83, 226, 208, 42, 117, 88, 121, 232, 77, 143, 135, 145, 246, 193, 20, 2, 17, 0, 0, 0, 12, 54, 254, 101, 87, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: