Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ff03d00314576f3c762dd5d4ece9e41434ba96053995ed79b448ac0e86ee984

Tx prefix hash: 0f5d104854a0942b55973573bfd3f30847495f5983ed6b19487c192b620d6840
Tx public key: 2bd0c689c0f5f0595bb0482d38887ce0a5c870783ad83bf03fd2c3801e2fdc18
Timestamp: 1774152966 Timestamp [UTC]: 2026-03-22 04:16:06 Age [y:d:h:m:s]: 00:241:23:27:42
Block: 1503107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178501 RingCT/type: yes/0
Extra: 012bd0c689c0f5f0595bb0482d38887ce0a5c870783ad83bf03fd2c3801e2fdc18021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 461828086c277037e718ac4371653b42f67fb6f88a286bedb5559b6d83b20c1d 0.000600000000 1992811 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": 1503117, "vin": [ { "gen": { "height": 1503107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461828086c277037e718ac4371653b42f67fb6f88a286bedb5559b6d83b20c1d" } } ], "extra": [ 1, 43, 208, 198, 137, 192, 245, 240, 89, 91, 176, 72, 45, 56, 136, 124, 224, 165, 200, 112, 120, 58, 216, 59, 240, 63, 210, 195, 128, 30, 47, 220, 24, 2, 17, 0, 0, 0, 2, 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: