Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38679fa088a71d394dd7995cb44f0d7b5bb3814b0144a06ed70b1bbdb1bcfbe

Tx prefix hash: ab4dd7a572c7ae7286f4ce53db1304a2f26d78ca64a2e0fbc72f34d48cd5d8a4
Tx public key: bed561776da811e5fe3cf7a0a3843131e9f689c4b54cf1460c3e2e01e938e56e
Timestamp: 1770111611 Timestamp [UTC]: 2026-02-03 09:40:11 Age [y:d:h:m:s]: 00:285:03:13:34
Block: 1469679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209223 RingCT/type: yes/0
Extra: 01bed561776da811e5fe3cf7a0a3843131e9f689c4b54cf1460c3e2e01e938e56e021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ff2639dba9a3c244e8e504fc330c8a0af0c38fe9b8fda47532660b9c3a1dfb51 0.000600000000 1958943 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": 1469689, "vin": [ { "gen": { "height": 1469679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff2639dba9a3c244e8e504fc330c8a0af0c38fe9b8fda47532660b9c3a1dfb51" } } ], "extra": [ 1, 190, 213, 97, 119, 109, 168, 17, 229, 254, 60, 247, 160, 163, 132, 49, 49, 233, 246, 137, 196, 181, 76, 241, 70, 12, 62, 46, 1, 233, 56, 229, 110, 2, 17, 0, 0, 0, 5, 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: