← previous blocknext block →recent activity
Analyzing
Block #101,993,424
18 transactions · 18 stateful · 2026-09-04 20:18:37 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,993,424 · 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
1w02w17w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf139b130…d132
0x34b655…2a6f
4 touches
1 conflict
0xb9a0dde5…9e2b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda09bbc9…b41b
0x34b655…2a6f
4 touches
1 conflict
0xe0da07e4…ccf2
0x34b655…2a6f
4 touches
1 conflict
0xe53bd661…5352
0x34b655…2a6f
4 touches
1 conflict
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
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 0xf139b130f5…fdd132
Audit this contract →
← previous block·next block →recent activity