Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3502c2415b364b40c063178c8d01cb4a0b43ea09f5255da340f9ad9112f51bdc

Tx prefix hash: 702952abf27ce969a8d2633a89f788994217d7519340235772743cd89ef70a7a
Tx public key: f88c1f4ccb73153a288f4de0d70358e2616a79eddb0ccad2409197f48f321580
Timestamp: 1743207274 Timestamp [UTC]: 2025-03-29 00:14:34 Age [y:d:h:m:s]: 01:046:02:59:26
Block: 1249472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283830 RingCT/type: yes/0
Extra: 01f88c1f4ccb73153a288f4de0d70358e2616a79eddb0ccad2409197f48f3215800211000000029ba629df000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 90b16e525b4de56fdc8c40f787cb5a37a715a6c933ec7fa107c503658e6a1edb 0.000600000000 1736511 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": 1249482, "vin": [ { "gen": { "height": 1249472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90b16e525b4de56fdc8c40f787cb5a37a715a6c933ec7fa107c503658e6a1edb" } } ], "extra": [ 1, 248, 140, 31, 76, 203, 115, 21, 58, 40, 143, 77, 224, 215, 3, 88, 226, 97, 106, 121, 237, 219, 12, 202, 210, 64, 145, 151, 244, 143, 50, 21, 128, 2, 17, 0, 0, 0, 2, 155, 166, 41, 223, 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: