Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf99035ef2bbc78caba8a961418bfd54324e39c27acd663e48de1a6d41b7781c

Tx prefix hash: 81042d584411a758af5c101f7f561ff410e9457718e5d5bf1f71f40c5bbb8b6a
Tx public key: 91589d573bbe654e6010423b9c488302a1e523284afeea5854ae328db89ad525
Timestamp: 1771404778 Timestamp [UTC]: 2026-02-18 08:52:58 Age [y:d:h:m:s]: 00:272:13:12:06
Block: 1480366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200313 RingCT/type: yes/0
Extra: 0191589d573bbe654e6010423b9c488302a1e523284afeea5854ae328db89ad52502110000000cf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3b9a65e7de7796f558a71d34cfb3a6f1ded236b3f248352ba8d793306f5947b1 0.000600000000 1969734 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": 1480376, "vin": [ { "gen": { "height": 1480366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b9a65e7de7796f558a71d34cfb3a6f1ded236b3f248352ba8d793306f5947b1" } } ], "extra": [ 1, 145, 88, 157, 87, 59, 190, 101, 78, 96, 16, 66, 59, 156, 72, 131, 2, 161, 229, 35, 40, 74, 254, 234, 88, 84, 174, 50, 141, 184, 154, 213, 37, 2, 17, 0, 0, 0, 12, 241, 136, 200, 168, 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: