← previous blocknext block →recent activity
Analyzing
Block #107,841,998
31 transactions · 21 stateful · 2026-09-25 08:11:36 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,841,998 · 31 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
4w05w18w09w113w016w117w018w119w220w321w424w025w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ff9db2e…22f6
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x508174fb…94d2
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x6ace66bb…7cde
0x34b655…2a6f
4 touches
1 conflict
0x6aeef401…c7f2
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 0x3ff9db2e2d…9122f6
Audit this contract →
← previous block·next block →recent activity