Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 458ae1b514d7b8fe19b9e4a1bfed3a3298ddee365dba497f721fdf5cc177856c

Tx prefix hash: 57b5f3251fc6ed2dc455c071fdf9a07c5cc188ccc31aa14776f1c793e57c61f4
Tx public key: 1698a75f5bc7d112dda456e638467323094cbc0e9b42b9ee12e3d4d22ba1d10a
Timestamp: 1736512215 Timestamp [UTC]: 2025-01-10 12:30:15 Age [y:d:h:m:s]: 01:225:21:43:02
Block: 1194305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425565 RingCT/type: yes/0
Extra: 011698a75f5bc7d112dda456e638467323094cbc0e9b42b9ee12e3d4d22ba1d10a021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6c71e244a5c36d6ade134993159cc3712d23b078dcd26aa5c2c016d260ef69b 0.000600000000 1680874 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": 1194315, "vin": [ { "gen": { "height": 1194305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6c71e244a5c36d6ade134993159cc3712d23b078dcd26aa5c2c016d260ef69b" } } ], "extra": [ 1, 22, 152, 167, 95, 91, 199, 209, 18, 221, 164, 86, 230, 56, 70, 115, 35, 9, 76, 188, 14, 155, 66, 185, 238, 18, 227, 212, 210, 43, 161, 209, 10, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: