← previous blocknext block →recent activity
Analyzing
Block #105,436,025
24 transactions · 23 stateful · 2026-09-16 22:16:06 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,436,025 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w18w09w111w012w114w215w117w318w419w520w622w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xf5606832…7b26
0x34b655…2a6f
8 touches
6 conflicts
0x89bc46ca…94c4
0x34b655…2a6f
8 touches
6 conflicts
0xd1448207…452d
0x34b655…2a6f
6 touches
3 conflicts
0x9752e14d…7888
0x34b655…2a6f
6 touches
3 conflicts
0x0f94e353…1f32
0x34b655…2a6f
4 touches
1 conflict
0x161d8cf7…654b
0x34b655…2a6f
4 touches
1 conflict
0x4118bd12…924a
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
6 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity