Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 987fc7b344e15f9f3418971498d5be4d2cd5436d8d416f7b3cfb12c3f8747123

Tx prefix hash: 618c45b3e61cb3dcd17ae4124c717a34d4ca907f8aac926ffd0a68164e29964b
Tx public key: aa01a551f905b20ca4244771268e6a9b6fa154f34eb3cb286f6bdc2505a4ad0a
Timestamp: 1722458307 Timestamp [UTC]: 2024-07-31 20:38:27 Age [y:d:h:m:s]: 02:111:22:56:16
Block: 1077933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604966 RingCT/type: yes/0
Extra: 01aa01a551f905b20ca4244771268e6a9b6fa154f34eb3cb286f6bdc2505a4ad0a021100000002e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 79cc8ef9f9b75746dd34a8c9589468c4f1bedd41d9234ef001674b29a20d45b4 0.000600000000 1550488 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 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": 1077943, "vin": [ { "gen": { "height": 1077933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79cc8ef9f9b75746dd34a8c9589468c4f1bedd41d9234ef001674b29a20d45b4" } } ], "extra": [ 1, 170, 1, 165, 81, 249, 5, 178, 12, 164, 36, 71, 113, 38, 142, 106, 155, 111, 161, 84, 243, 78, 179, 203, 40, 111, 107, 220, 37, 5, 164, 173, 10, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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: