← previous blocknext block →recent activity
Analyzing
Block #83,630,405
18 transactions · 14 stateful · 2026-06-25 15:49:02 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,630,405 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w012w013w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0xd7add284…8d28
0x34b655…2a6f
4 touches
1 conflict
0x0d5e464a…aa7e
0x34b655…2a6f
2 touches
0 conflicts
0x54daebc3…98e1
0x34b655…2a6f
2 touches
0 conflicts
0x6713b018…05f3
0x34b655…2a6f
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x5a5dd7b4d7…36fba4
Audit this contract →
← previous block·next block →recent activity