Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77fd3a7af9178f9b8d11ae34cfe366ad8e073d16b65abea8a16bdae0678ea531

Tx prefix hash: a765060a6c3ec8682848d030af123eaf24c5891debf6c11198714966308f5052
Tx public key: e631788443398cadd85c912ce03f53ce129f77deeac1cbfa31414f53f0b8dbf8
Timestamp: 1772648620 Timestamp [UTC]: 2026-03-04 18:23:40 Age [y:d:h:m:s]: 00:262:02:20:45
Block: 1490672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192822 RingCT/type: yes/0
Extra: 01e631788443398cadd85c912ce03f53ce129f77deeac1cbfa31414f53f0b8dbf8021100000010e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 98703ad08920f20fdd156d19d71b6e3644eefd0023a73d5048119d4b2ce98419 0.000600000000 1980178 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": 1490682, "vin": [ { "gen": { "height": 1490672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98703ad08920f20fdd156d19d71b6e3644eefd0023a73d5048119d4b2ce98419" } } ], "extra": [ 1, 230, 49, 120, 132, 67, 57, 140, 173, 216, 92, 145, 44, 224, 63, 83, 206, 18, 159, 119, 222, 234, 193, 203, 250, 49, 65, 79, 83, 240, 184, 219, 248, 2, 17, 0, 0, 0, 16, 228, 245, 25, 63, 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: