Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69bfc4e2debf22544d8d31e93a740713c39ddb6ffae2c8f73c167ab128c8d89e

Tx prefix hash: 37554faae8dc8009656c5cf7f6ba1535b84c70f0cfbafa822300a0b65148f02e
Tx public key: 45fae61382edc8742e8d0cef285d85946e3ffb9828576b91e1497148dae2e357
Timestamp: 1771489759 Timestamp [UTC]: 2026-02-19 08:29:19 Age [y:d:h:m:s]: 00:271:21:15:28
Block: 1481083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199837 RingCT/type: yes/0
Extra: 0145fae61382edc8742e8d0cef285d85946e3ffb9828576b91e1497148dae2e357021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e09b4d03174513e589a2788af23941386d08a7b5cf93c99b13ad100baa4ac5cb 0.000600000000 1970457 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": 1481093, "vin": [ { "gen": { "height": 1481083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e09b4d03174513e589a2788af23941386d08a7b5cf93c99b13ad100baa4ac5cb" } } ], "extra": [ 1, 69, 250, 230, 19, 130, 237, 200, 116, 46, 141, 12, 239, 40, 93, 133, 148, 110, 63, 251, 152, 40, 87, 107, 145, 225, 73, 113, 72, 218, 226, 227, 87, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: