← previous blocknext block →recent activity
Analyzing
Block #100,455,624
16 transactions · 16 stateful · 2026-08-30 11:17:23 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,455,624 · 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
2w04w05w18w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe45073e…6315
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x0960ac51…5440
0x34b655…2a6f
2 touches
0 conflicts
0x0c7deec4…77cb
0x34b655…2a6f
2 touches
0 conflicts
0x272b9268…c528
0x34b655…2a6f
2 touches
0 conflicts
0x2bd6a2cb…a8e5
0x34b655…2a6f
2 touches
0 conflicts
0x41c56387…a8f6
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 0xfe45073ed9…0c6315
Audit this contract →
← previous block·next block →recent activity