Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b19059cc5a4e774cc3f00561a68e2e6c98bedd027f29bc96704d38df3a403a1

Tx prefix hash: f7d453f5d092273e1b385450cba574b6c6691bc6accb8d75bb6d74055f03b98e
Tx public key: e3fd5ea4fe3d3e305ab905e98388340e18cec440b1a92ad3e5c33536a8501ac8
Timestamp: 1759433310 Timestamp [UTC]: 2025-10-02 19:28:30 Age [y:d:h:m:s]: 01:043:04:43:35
Block: 1381356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297146 RingCT/type: yes/0
Extra: 01e3fd5ea4fe3d3e305ab905e98388340e18cec440b1a92ad3e5c33536a8501ac8021100000007a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cede3510ceb7215c508cd545bffa8c94237fca9d83597d9a96a90fd99d36bfa3 0.000600000000 1869475 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": 1381366, "vin": [ { "gen": { "height": 1381356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cede3510ceb7215c508cd545bffa8c94237fca9d83597d9a96a90fd99d36bfa3" } } ], "extra": [ 1, 227, 253, 94, 164, 254, 61, 62, 48, 90, 185, 5, 233, 131, 136, 52, 14, 24, 206, 196, 64, 177, 169, 42, 211, 229, 195, 53, 54, 168, 80, 26, 200, 2, 17, 0, 0, 0, 7, 165, 220, 205, 121, 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: