Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa2bb8039640575eb9569697115d64041171cad02b3655e34049b2cdb1a31939

Tx prefix hash: e8d15a056727ff948916b5f2b4cfd4991649e1ffd463ef99fcaba2256a0f4dc5
Tx public key: 59d31e4501ccd8f9b6e44de5fe2f8c9e2aec1c8ca37fabd0473417e6b00270ce
Timestamp: 1578663360 Timestamp [UTC]: 2020-01-10 13:36:00 Age [y:d:h:m:s]: 06:258:00:53:29
Block: 42734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1599137 RingCT/type: yes/0
Extra: 0159d31e4501ccd8f9b6e44de5fe2f8c9e2aec1c8ca37fabd0473417e6b00270ce021100000007d81c26c0000000000000000000

1 output(s) for total of 0.443001668468 xmr

stealth address amount amount idx tag
00: 752ee5de1ef03f3bc84cb0f18277835c728bfa2529fc2cb022ef1e34d6984ce5 0.443001668468 77082 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": 42744, "vin": [ { "gen": { "height": 42734 } } ], "vout": [ { "amount": 443001668468, "target": { "key": "752ee5de1ef03f3bc84cb0f18277835c728bfa2529fc2cb022ef1e34d6984ce5" } } ], "extra": [ 1, 89, 211, 30, 69, 1, 204, 216, 249, 182, 228, 77, 229, 254, 47, 140, 158, 42, 236, 28, 140, 163, 127, 171, 208, 71, 52, 23, 230, 176, 2, 112, 206, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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: