← previous blocknext block →recent activity
Analyzing
Block #100,916,855
16 transactions · 13 stateful · 2026-09-01 01:57:58 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,916,855 · 16 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
4w014w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb88ed4e…a342
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x05adb823…6582
0x34b655…2a6f
2 touches
0 conflicts
0x200ac9da…b4db
0x34b655…2a6f
2 touches
0 conflicts
0x3eb33a35…5bb4
0x34b655…2a6f
2 touches
0 conflicts
0x4e4b3596…413b
0x34b655…2a6f
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 0xeb88ed4e17…eaa342
Audit this contract →
← previous block·next block →recent activity