Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa76f02472ae3c65e4baeeb11b436c1bafd78e6bb75137f1c90be83b65fa5a0

Tx prefix hash: 4be4232437a84917ca8e7de89e851b06a1c25f9918e913410d802018a20d4a32
Tx public key: 20f941f7fcf25386aa58e5b30a162f4481010b46dec78511301b3c901ce42948
Timestamp: 1773839262 Timestamp [UTC]: 2026-03-18 13:07:42 Age [y:d:h:m:s]: 00:241:09:41:32
Block: 1500503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177959 RingCT/type: yes/0
Extra: 0120f941f7fcf25386aa58e5b30a162f4481010b46dec78511301b3c901ce42948021100000019f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9522aa2233a8de4dc71049e093578e3e182813471853bf16d8fb9e0c8171b278 0.000600000000 1990175 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": 1500513, "vin": [ { "gen": { "height": 1500503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9522aa2233a8de4dc71049e093578e3e182813471853bf16d8fb9e0c8171b278" } } ], "extra": [ 1, 32, 249, 65, 247, 252, 242, 83, 134, 170, 88, 229, 179, 10, 22, 47, 68, 129, 1, 11, 70, 222, 199, 133, 17, 48, 27, 60, 144, 28, 228, 41, 72, 2, 17, 0, 0, 0, 25, 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: