Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6338fc2b02293bc182478cc57a5c0a3422d151c616a2ebeefdec9f11dfb5c89a

Tx prefix hash: badfd26edd0f0198aba1a41fb5fc28226d699bb00ef5af2800b0eb837ee4d2a8
Tx public key: 61f555a019a94757c7951f7805076713e007af56c3b1a5c381211e10949bc180
Timestamp: 1579037646 Timestamp [UTC]: 2020-01-14 21:34:06 Age [y:d:h:m:s]: 06:126:00:35:00
Block: 45609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1491463 RingCT/type: yes/0
Extra: 0161f555a019a94757c7951f7805076713e007af56c3b1a5c381211e10949bc1800211000001022264afe6000000000000000000

1 output(s) for total of 0.433390402150 xmr

stealth address amount amount idx tag
00: d68ec4e02785aa538aaa03d5e09863b9daa6641804a1ec4e0eb3d4caa6fc12b9 0.433390402150 83433 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": 45619, "vin": [ { "gen": { "height": 45609 } } ], "vout": [ { "amount": 433390402150, "target": { "key": "d68ec4e02785aa538aaa03d5e09863b9daa6641804a1ec4e0eb3d4caa6fc12b9" } } ], "extra": [ 1, 97, 245, 85, 160, 25, 169, 71, 87, 199, 149, 31, 120, 5, 7, 103, 19, 224, 7, 175, 86, 195, 177, 165, 195, 129, 33, 30, 16, 148, 155, 193, 128, 2, 17, 0, 0, 1, 2, 34, 100, 175, 230, 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: