Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77b9aa7c8a8e120d2f4b57c7687f90d59d1d510f2b151c0a8b364e168f422e61

Tx prefix hash: 3ee5581b6931040e62b2d8d855001c708973e18841fed2bdf6b7169d322c08ad
Tx public key: c837a483a76270ce321d34bca00b83756a1bb710b752db7c3507d209a1544cc6
Timestamp: 1578833706 Timestamp [UTC]: 2020-01-12 12:55:06 Age [y:d:h:m:s]: 06:313:14:50:30
Block: 43972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1638404 RingCT/type: yes/0
Extra: 01c837a483a76270ce321d34bca00b83756a1bb710b752db7c3507d209a1544cc602110000000dd81c26c0000000000000000000

1 output(s) for total of 0.438837115919 xmr

stealth address amount amount idx tag
00: e2f2fbc89ac839c8d5e96ac8914dd0c4e4b2e1298d707937c8e68383b274ccf5 0.438837115919 79845 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": 43982, "vin": [ { "gen": { "height": 43972 } } ], "vout": [ { "amount": 438837115919, "target": { "key": "e2f2fbc89ac839c8d5e96ac8914dd0c4e4b2e1298d707937c8e68383b274ccf5" } } ], "extra": [ 1, 200, 55, 164, 131, 167, 98, 112, 206, 50, 29, 52, 188, 160, 11, 131, 117, 106, 27, 183, 16, 183, 82, 219, 124, 53, 7, 210, 9, 161, 84, 76, 198, 2, 17, 0, 0, 0, 13, 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: