Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0112dd332deaa4f245a01edc63801fe5165dddb502cec6c509bb42e186e91be5

Tx prefix hash: f1a00906e303f7dda3f0ccf39f94c8d849dbb1799a1a46c4eafbac146c4290c7
Tx public key: 897e40dfd654648934b992c07dabedb264181343fee7eb08a41122c08954eb03
Timestamp: 1744145484 Timestamp [UTC]: 2025-04-08 20:51:24 Age [y:d:h:m:s]: 01:219:16:03:33
Block: 1257228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420924 RingCT/type: yes/0
Extra: 01897e40dfd654648934b992c07dabedb264181343fee7eb08a41122c08954eb0302110000000b6c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b9d002a4fcf1af8a1a9d6c93ef9dbab3c82b795cfbe30d737f87ecf94815b18a 0.000600000000 1744347 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": 1257238, "vin": [ { "gen": { "height": 1257228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d002a4fcf1af8a1a9d6c93ef9dbab3c82b795cfbe30d737f87ecf94815b18a" } } ], "extra": [ 1, 137, 126, 64, 223, 214, 84, 100, 137, 52, 185, 146, 192, 125, 171, 237, 178, 100, 24, 19, 67, 254, 231, 235, 8, 164, 17, 34, 192, 137, 84, 235, 3, 2, 17, 0, 0, 0, 11, 108, 152, 170, 61, 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: