Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 031b5be9b261b3059720200d720ed18c8f6778f3a77bca13ea9b3d83fb91d2e6

Tx prefix hash: b58c46d44aafc948900aeff4d0435e51f6560b50e49bf0d523c97740b20b477a
Tx public key: 891a12f4fde3d386f10f614cc13cf8df7532b3344243cc867e300963e155257c
Timestamp: 1771635294 Timestamp [UTC]: 2026-02-21 00:54:54 Age [y:d:h:m:s]: 00:270:18:57:29
Block: 1482287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199065 RingCT/type: yes/0
Extra: 01891a12f4fde3d386f10f614cc13cf8df7532b3344243cc867e300963e155257c021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5f1bfa7ed8a34982c837256fc0755ac65a52d354723304664dc9243ac4afed30 0.000600000000 1971679 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": 1482297, "vin": [ { "gen": { "height": 1482287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f1bfa7ed8a34982c837256fc0755ac65a52d354723304664dc9243ac4afed30" } } ], "extra": [ 1, 137, 26, 18, 244, 253, 227, 211, 134, 241, 15, 97, 76, 193, 60, 248, 223, 117, 50, 179, 52, 66, 67, 204, 134, 126, 48, 9, 99, 225, 85, 37, 124, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: