← previous blocknext block →recent activity
Analyzing
Block #100,984,382
22 transactions · 20 stateful · 2026-09-01 07:37:38 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,984,382 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w08w010w111w112w013w115w016w017w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
4 touches
1 conflict
0x10abefc9…c9bc
0x34ae4d…3fc5
4 touches
1 conflict
0x10d80fee…dbda
0x34ae4d…3fc5
4 touches
1 conflict
0x40970e69…da50
0x34ae4d…3fc5
4 touches
1 conflict
0x8cf3d245…1d0d
0x34ae4d…3fc5
4 touches
1 conflict
0xb05cd4f5…73d0
0x34ae4d…3fc5
4 touches
1 conflict
0xdb067026…9eb8
0x34ae4d…3fc5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity