← previous blocknext block →recent activity
Analyzing
Block #100,048,224
19 transactions · 19 stateful · 2026-08-29 01:03:08 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,048,224 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w17w18w29w010w111w312w413w514w617w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1813378d…cec7
0x34b655…2a6f
10 touches
10 conflicts
0x6d5c5d72…914b
0x34b655…2a6f
10 touches
10 conflicts
0x4e43b99d…f545
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
6 touches
3 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
6 touches
3 conflicts
0x5312402f…0d71
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x1813378dde…90cec7
Audit this contract →
← previous block·next block →recent activity