← previous blocknext block →recent activity
Analyzing
Block #108,470,004
16 transactions · 15 stateful · 2026-09-27 12:52:17 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,470,004 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc856ff11…2b9c
0x34b655…2a6f
4 touches
1 conflict
0xcd0e79e1…4c56
0x34b655…2a6f
4 touches
1 conflict
0xe3254525…23a6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x17c3cde7…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x351f0da2…ed99
0x34b655…2a6f
4 touches
1 conflict
0x37f93b32…cc57
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
1 conflict on slot 0xc856ff1166…d02b9c
Audit this contract →
← previous block·next block →recent activity