Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 869b0c5a1f944d00582427bfc087f35d48b339aca9d14f42e17d64baf5e7b3d2

Tx prefix hash: 4b736ad6dced5bbc3ffbbf538b2144e0bca77f5c2e9d064ae3579d5d3fe8319d
Tx public key: db8a0fede1a5916ed479c0720026cd5845afe148ff7ffa8d1ad14a14d45c446b
Timestamp: 1773047367 Timestamp [UTC]: 2026-03-09 09:09:27 Age [y:d:h:m:s]: 00:254:12:26:33
Block: 1493957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187446 RingCT/type: yes/0
Extra: 01db8a0fede1a5916ed479c0720026cd5845afe148ff7ffa8d1ad14a14d45c446b021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f98a5cb2c1b1b468e9ae1b65b9e2fc1d54db3910916345f2ce12a20873bc2c28 0.000600000000 1983523 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": 1493967, "vin": [ { "gen": { "height": 1493957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f98a5cb2c1b1b468e9ae1b65b9e2fc1d54db3910916345f2ce12a20873bc2c28" } } ], "extra": [ 1, 219, 138, 15, 237, 225, 165, 145, 110, 212, 121, 192, 114, 0, 38, 205, 88, 69, 175, 225, 72, 255, 127, 250, 141, 26, 209, 74, 20, 212, 92, 68, 107, 2, 17, 0, 0, 0, 1, 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: