← previous blocknext block →recent activity
Analyzing
Block #100,028,181
16 transactions · 13 stateful · 2026-08-28 23:22:15 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,028,181 · 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
7w08w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64f45fcd…0f55
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0xf275b4ca…57b8
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x5c1a0788…7fc1
0xe52b14…7230
3 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
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 0x64f45fcd12…1c0f55
Audit this contract →
← previous block·next block →recent activity