← previous blocknext block →recent activity
Analyzing
Block #100,420,016
13 transactions · 13 stateful · 2026-08-30 08:18:08 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,420,016 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w08w19w310w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee757899…302b
0x34b655…2a6f
6 touches
3 conflicts
0x00c8447e…a888
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x1db5837f…1264
0x34b655…2a6f
6 touches
3 conflicts
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0x07d94be1…7fa8
0x34b655…2a6f
4 touches
1 conflict
0x27034002…2f27
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0xee7578993b…85302b
Audit this contract →
← previous block·next block →recent activity