Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61be84ece4958d0d95dcfd6b767be73bde92c4ac66ea4d0f59b4b66cc2db5e6f

Tx prefix hash: 1b46758527649d3116a0a18ec8e87fe48fb2c9c8d94b7cc1603f3846ac52803c
Tx public key: 6cd542d3c31ba221748eeacde24350f31f99b39db07b104bc8ce568086f6f80f
Timestamp: 1775162108 Timestamp [UTC]: 2026-04-02 20:35:08 Age [y:d:h:m:s]: 00:229:20:28:49
Block: 1511459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169806 RingCT/type: yes/0
Extra: 016cd542d3c31ba221748eeacde24350f31f99b39db07b104bc8ce568086f6f80f021100000003e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e32e071ecfd1e4f01076f1f45ab6d5bb4aa279fdbff14fa039df4f696884cb8d 0.000600000000 2001251 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": 1511469, "vin": [ { "gen": { "height": 1511459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e32e071ecfd1e4f01076f1f45ab6d5bb4aa279fdbff14fa039df4f696884cb8d" } } ], "extra": [ 1, 108, 213, 66, 211, 195, 27, 162, 33, 116, 142, 234, 205, 226, 67, 80, 243, 31, 153, 179, 157, 176, 123, 16, 75, 200, 206, 86, 128, 134, 246, 248, 15, 2, 17, 0, 0, 0, 3, 227, 215, 220, 159, 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: