Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe65a5faf5ea0907a326a8aaaf0ab7f5b6c1f8a10c00eb1c5daa85eb8a256272

Tx prefix hash: c381431785b2e43915ec8aca28627791e394e3be7cafc0871d0d409d57d0036e
Tx public key: 47aece87dfe1deba30bbf5c987e59a1d4d35e5bdf460f1aaf10cc9bbcdd0fe24
Timestamp: 1749428398 Timestamp [UTC]: 2025-06-09 00:19:58 Age [y:d:h:m:s]: 01:165:17:14:51
Block: 1300995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382499 RingCT/type: yes/0
Extra: 0147aece87dfe1deba30bbf5c987e59a1d4d35e5bdf460f1aaf10cc9bbcdd0fe2402110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fd878c2a65a3f743dc34574f7954279a13073f37e3b075ae0060177d74b7b39a 0.000600000000 1788548 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": 1301005, "vin": [ { "gen": { "height": 1300995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd878c2a65a3f743dc34574f7954279a13073f37e3b075ae0060177d74b7b39a" } } ], "extra": [ 1, 71, 174, 206, 135, 223, 225, 222, 186, 48, 187, 245, 201, 135, 229, 154, 29, 77, 53, 229, 189, 244, 96, 241, 170, 241, 12, 201, 187, 205, 208, 254, 36, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: