Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f6e2a03408ef8f7c9b9db0e7c111064e42f145e5e3a8b30eef0c31b3788b3cc

Tx prefix hash: 969a269e9cba1b905cb4ea8e16a9a3acdafd56177a35e0ef9e86e5bce6213fe6
Tx public key: 8b26d25a941a9c1db4e7219212c248f60c1b6898f29fad48434de6e0e5c388ef
Timestamp: 1792061585 Timestamp [UTC]: 2026-10-15 10:53:05 Age [y:d:h:m:s]: 00:034:22:43:00
Block: 1654939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 26854 RingCT/type: yes/0
Extra: 018b26d25a941a9c1db4e7219212c248f60c1b6898f29fad48434de6e0e5c388ef

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e2b75ced1790dd7f1a13b5693292a29e79fa29ef10d46de8b555fecb4eb586bd 0.000600000000 2145649 of 15 <b1>

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": 1654949, "vin": [ { "gen": { "height": 1654939 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "e2b75ced1790dd7f1a13b5693292a29e79fa29ef10d46de8b555fecb4eb586bd", "view_tag": "b1" } } } ], "extra": [ 1, 139, 38, 210, 90, 148, 26, 156, 29, 180, 231, 33, 146, 18, 194, 72, 246, 12, 27, 104, 152, 242, 159, 173, 72, 67, 77, 230, 224, 229, 195, 136, 239 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: