Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be73350751df7431e86a768633cbe2ececa9f22f2e1b449fbdb12df7c658cae7

Tx prefix hash: dc61328d3d24b6f92f00c20ea43330ae47a032b687f2a22458139ff522c9fb09
Tx public key: b3815eef8b69b04f5b4179c8a5ae06047fb0fea92c651e712ff11f2605de94ac
Timestamp: 1746090938 Timestamp [UTC]: 2025-05-01 09:15:38 Age [y:d:h:m:s]: 01:199:15:16:53
Block: 1273331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406689 RingCT/type: yes/0
Extra: 01b3815eef8b69b04f5b4179c8a5ae06047fb0fea92c651e712ff11f2605de94ac021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf07f209dc9bc97a1f67e197317174cf61e01c8240b8eb8b5eb15c964d12ac42 0.000600000000 1760612 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": 1273341, "vin": [ { "gen": { "height": 1273331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf07f209dc9bc97a1f67e197317174cf61e01c8240b8eb8b5eb15c964d12ac42" } } ], "extra": [ 1, 179, 129, 94, 239, 139, 105, 176, 79, 91, 65, 121, 200, 165, 174, 6, 4, 127, 176, 254, 169, 44, 101, 30, 113, 47, 241, 31, 38, 5, 222, 148, 172, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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: