Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e64d16ff4f02ba999960c304694a3324347c2c0e5d6f293a5f95db2e4417adef

Tx prefix hash: b8306e2e788c746f88317619b57990948e067f5f9bb0079e8e1b770ded2099b8
Tx public key: b0f17f0b3cd38b4f099645cbe9d209193c16cb80d71097cc4f0bf2a2bc475535
Timestamp: 1774207300 Timestamp [UTC]: 2026-03-22 19:21:40 Age [y:d:h:m:s]: 00:240:12:25:25
Block: 1503551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177428 RingCT/type: yes/0
Extra: 01b0f17f0b3cd38b4f099645cbe9d209193c16cb80d71097cc4f0bf2a2bc475535021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 685b80eb2e7c546aa84ccc4a76946748a34962ffa5a3079d73a116ff7131e1a9 0.000600000000 1993263 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": 1503561, "vin": [ { "gen": { "height": 1503551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "685b80eb2e7c546aa84ccc4a76946748a34962ffa5a3079d73a116ff7131e1a9" } } ], "extra": [ 1, 176, 241, 127, 11, 60, 211, 139, 79, 9, 150, 69, 203, 233, 210, 9, 25, 60, 22, 203, 128, 215, 16, 151, 204, 79, 11, 242, 162, 188, 71, 85, 53, 2, 17, 0, 0, 0, 1, 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: